Chapel (Cray Inc. HPCS Language)
Cascade high productivity language
Chapel is a parallel programming language that emerged from Cray Inc.’s participation in the High Productivity Computing Systems (HPCS) program sponsored by the Defense Advanced Research Projects Agency (DARPA). The name Chapel derives from the phrase “Cascade High Productivity Language,” where “Cascade” is the project name for the Cray HPCS effort. The HPCS program was launched with the goal of raising user productivity on large-scale parallel systems by a factor of ten. Chapel was designed to help with this challenge by vastly improving the programmability of parallel architectures while matching or beating the performance, portability, and robustness of previous parallel programming models.
The Chapel language got its start in 2002 during the first phase of Cray Inc.’s participation in the DARPA HPCS program. While exploring candidate system design concepts to improve user productivity, the technical leaders...
This material is based upon work supported by the Defense Advanced Research Projects Agency under its Agreement No. HR0011-07-9-0001. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the Defense Advanced Research Projects Agency.
- 1.Callahan D, Chamberlain B, Zima H (April 2004) The Cascade high productivity language. 9th International workshop on high-level parallel programming models and supportive environments, pp 52–60, Santa Fe, NMGoogle Scholar
- 2.Chamberlain BL (November 2001) The design and implementation of a region-based parallel language. PhD thesis, University of WashingtonGoogle Scholar
- 3.Chamberlain BL (October 2007) Multiresolution languages for portable yet efficient parallel programming. http://chapel.cray.com/papers/DARPA-RFI-Chapel-web.pdf. Accessed 4 May 2011
- 5.Chamberlain BL, Deitz SJ, Hribar MB, Wong WA (November 2008) Chapel tutorial using global HPCC benchmarks: STREAM Triad, Random Access, and FFT (revision 1.6). http://chapel.cray.com/hpcc/hpccTutorial-1.6.pdf. Accessed 4 May 2011
- 6.Chamberlain BL, Deitz SJ, Iten D, Choi S-E (2010) User-defined distributions and layouts in Chapel: Philosophy and framework. In: Hot-PAR ‘10: Proceedings of the 2nd USENIX workshop on hot topics, June 2010Google Scholar
- 7.Chapel development site at SourceForge. http://sourceforge.net/projects/chapel. Accessed 4 May 2011
- 8.Chapel project website. http://chapel.cray.com. Accessed 4 May 2011
- 9.Cray Inc., Seattle, WA. Chapel Language Specification (version 0.796), October 2009. http://chapel.cray.com/papers.html. Accessed 4 May 2011
- 10.Cray Inc. Cray XMT Programming Environment User’s Guide, March 2009 (see http://docs.cray.com). Accessed 4 May 2011
- 11.Deitz SJ (2005) High-Level Programming Language Abstractions for Advanced and Dynamic Parallel Computations. PhD thesis, University of WashingtonGoogle Scholar
- 14.Feldman M, Chamberlain BL (2008) Closing the parallelism gap with the Chapel language. HPCWire, November 2008. http://www.hpcwire.com/hpcwire/2008-11-19/closing_the_paral lelism_gap_with_the_chapel_language.html. Accessed 4 May 2011
- 15.Koelbel CH, Loveman DB, Schreiber RS, Steele Jr GL, Zosel ME (September 1996) the High Performance Fortran handbook. Scientific and engineering computation. MIT Press, Cambridge, MAGoogle Scholar