Chapel
This document is the first published description of Chapel. It covers the core language design and major features. The sections of this document are:
Language Design
Language Implementations
Programming Guide
Syntax of Chapel Programs
This document describes the current (as of July 2011) vision for Chapel. Current status and plans for the development of Chapel are described in separate documents:
An Eclipse/RCP version of Chapel will be available by the end of 2011.
A paper describing the design of Chapel is available at
A description of the type system and abstract data types currently implemented in Chapel
Determining whether an abstract data type satisfies a property given a set of constraints
An example in Chapel of a program using a form of structured concurrency
Structure of Chapel Source Code
Chapel source code can be either in C, C++, or Fortran.
Source code for Chapel programs in C and Fortran can be compiled to either native code for C or Fortran (in which case the compiler is also itself written in Chapel) or bytecode for Chapel (in which case the compiler is written in C++ and then run through a bytecode compiler).
If the program is compiled in C++ with bytecode generation, the source code is compiled to bytecode and then de-compiled to native code (by running a command-line program).
Source code for Chapel programs in C or Fortran must compile to native code, and there is no bytecode available.
Source code for Chapel programs in Java can be either compiled to native code or compiled to.class files and then compiled to native code.
Source code for Chapel programs in Perl can be compiled to native code or compiled to.pl files and then compiled to native code.
Source code for Chapel programs in Python can be compiled to native code or compiled to.py files and then compiled to native code.
Source code for Chapel programs in Ruby can be compiled to native code or compiled to.rb files and then compiled to native code.
Please see the Chapel Language Guide
for information on the Chapel language itself, including compiler directives.
Determining Whether an Abstract Data Type Satisfies a Property in Chapel
An abstract data type in Chapel provides a type-safe way of solving certain kinds of problems.
For example, an abstract data type can be used to sort values (for example
Chapel [Updated] 2022
Chapel is an extension of the C programming language to support parallel computing.
Chapel is built from the ground up to utilize distributed memory systems efficiently.
The syntax and semantics of Chapel are intended to be as similar to the C programming language as possible.
Chapel is built on the strong foundation of C.
An important goal of Chapel is to bring the expressivity and conciseness of C into the large scale parallel computing world.
If ZPL is "C with memory and threads," then Chapel is "C with memory and parallelism."
Chapel supports the use of millions of threads per process for massively-parallel programming.
The architecture of Chapel is very flexible.
Chapel introduces flexible parallel scheduling to enable a programmer to dynamically load/unload threads as computation needs change.
Chapel is designed to maximize portability across parallel supercomputers, clusters, and workstations.
As part of the Natural Language Toolkit, Chapel is one of a group of libraries that together form the basis of a new generation of interactive educational and research tools for learning parallel computing.
Chapel supports easy access to threads via a combination of high level syntax and an object oriented type system.
It uses a type-safe, compiler-checked approach to concurrency.
There are multiple levels of concurrency: between threads, between data objects, and across processors.
The Chapel source code is distributed as a single file.
This is a simple single-file source file which compiles to a single executable binary file.
The distributed file contains a main function, and contains the compiled code of your program.
The distribution contains Chapel as a library.
If your system already has Chapel as a library, it will already be linked with your program.
Otherwise, you should be able to compile and run Chapel from the downloaded source file.
The distribution contains an optional file called: examples/chapel.c
This file is pre-compiled and comes with an example program.
If you are running Chapel from the downloaded source file, you should be able to simply rename the example program to your own program name.
The resulting executable is also named after your program name, by default: example_name.
When compiling your own program, Chapel should automatically create a proper link.
If the results are not what you expect, follow the next steps.
Create a file to hold the function and variable definitions of your program.
Include
f0d5c1b395

Related

Items