otherarchie's Profile

  • Name: Roch Archambault
  • Email: (Private)
  • Member Since: Nov 6, 2008
  • Last Logged In: Jul 20, 2009 3:10 PM
  • Status Level:  
  • Location: Toronto
  • Occupation: Compiler Architect and Compiler Focal Point for HPC
  • Biography: Roch is a Senior Technical Staff Member at the IBM Toronto Lab in the compiler development area. His most significant contributions have been as an architect and technical lead in compiler back-end and optimization technologies for IBM C, C++, and FORTRAN compiler products. He has actively participated in High Performance Computing (HPC) customer bid situations and played an important role supporting IBM HPC marketing teams. Mr. Archambault has extensive experience in inventing and producing code in the form of prototypes or fully implemented features and is well known for his in-depth knowledge of compiler and optimization technologies.
  • Expertise: Performance analysis, Compiler Optimization, Compiler Infrastructure

otherarchie's Latest Content

Welcome to the blog on Scientific Computing with C/C++.

IBM has a long history of Scientific Computing starting with the creation of FORTRAN
in 1957 to the control systems for the Apollo missions in the 1960s.

Today, various user groups and wikis exist to support IBM’s scientific computer users:


My Name is Roch Archambault and I have over 20 years of compiler development experience at IBM.

In the last 5 years I’ve been the compiler focal point for High Performance Computing (HPC). I’ve been involved with several high profile US government funded scientific computing efforts:
  • ASCI (Advanced Strategic Computing Initiative) since 1997 funded by DOE
  • HPCS (High Productivity Computing Systems) funded by DARPA.
  • Bluewater system (Great Lakes Consortium) funded by NSF.

The C and C++ languages are becoming more and more popular in Scientific Computing.

My colleagues and I hope to bring a wealth of expertise to this blog to assist programmers of scientific applications in analyzing and improving the performance of their codes.

0 Comments Permalink

Brainstorm with co-workers, get your questions answered, build status with your responses.

Write your own drafts, invite selected collaborators, or leave it open for all to pitch in.