Timothy Smith Email & Phone Number

Minneapolis, Mn, Us

Greater Minneapolis-St. Paul Area

Compiler developer for Cray's supercomputer compiler, which is based on the open-source LLVM compiler toolkit project. My primary project has been to use GIT wizardry to bring Cray's compiler up-to-date with upstream LLVM. Both Cray's compiler and upstream LLVM are large projects, each containing thousands of files and hundreds of thousands of lines of code. Cray's compiler had fallen three years behind upstream at the time of my hiring, and is now up-to-date. My current primary responsibility is keeping the Cray compiler up-to-date with upstream LLVM, as well as bug fixing and new feature development, mostly related to changes coming in from upstream. As a result of these efforts, Cray's compiler now leverages the latest features and enhancements from the upstream community, and Cray is no longer expending resources to fix bugs that had already been fixed upstream.

Hillsboro, Oregon

Validation tool developer, 2011-2016. Worked as an early member of a global grass-roots initiative within the company to create a CPU architecture validation tool that could be used by all CPU design teams. This tool (Maestro) would replace the costly, siloed, incompatible validation environments that had evolved at each design site. We based Maestro on the open-source LLVM compiler toolkit, making extensive modifications to transform it into a flexible low-level validation environment. Developed core plumbing features as well as graphics and power management validation features in C++ as part of an Agile team, and developed unit and integration tests for those features using gtest and LLVM's LIT environment. Worked extensively with our customers, developing training materials and delivering training seminars at sites around the world to help them use Maestro effectively. Earned recognition for ability to grasp customers' needs, drive feature definitions based on those needs, and train them then to use the new features effectively.Validation Engineer, 2002-2010. Developed low-level software in C and assembly to test architectural features of Intel's desktop, mobile, and server CPUs. Used hardware simulators to test these features while the CPU was in its design phase, and worked on the "first boot" teams to bring up and test early engineering samples of physical CPUs as well. Primarily responsible for testing microcode and power management features as part of a globally dispersed team. Found hardware and firmware bugs prior to product launch that saved the company from mitigation costs and brand damage.