FANDOM


Chapel
File:Cray Chapel Logo.png
Chapel logo
Paradigm(s) Object-oriented
Partitioned global address space
Parallel programming
Designed by Brad Chamberlain
Developer Cray Inc.
Preview release 1.6.0 (Template:Start date and age)
Influenced by HPF, ZPL
Usual filename extensions .chpl

Chapel, the Cascade High Productivity Language, is a parallel programming language developed by Cray.[1] It is being developed as part of the Cray Cascade project, a participant in DARPA's High Productivity Computing Systems (HPCS) program, which had the goal of increasing supercomputer productivity by the year 2010. Chapel aims to improve the programmability of parallel computers in general and the Cascade system in particular, by providing a higher level of expression than current programming languages do and by improving the separation between algorithmic expression and data structure implementation details.

Chapel supports a multithreaded parallel programming model at a high level by supporting abstractions for data parallelism, task parallelism, and nested parallelism. It enables optimizations for the locality of data and computation in the program via abstractions for data distribution and data-driven placement of subcomputations. It allows for code reuse and generality through object-oriented concepts and generic programming features. For instance, Chapel allows for the declaration of locales.[2]

While Chapel borrows concepts from many preceding languages, its parallel concepts are most closely based on ideas from High Performance Fortran (HPF), ZPL, and the Cray MTA's extensions to Fortran and C.

It is being developed as an open source project, under the BSD license.[3]

See also Edit

Template:Portal

NotesEdit

Template:Reflist

ReferencesEdit

External linksEdit


Cite error: <ref> tags exist, but no <references/> tag was found

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.