[LBNL]

Berkeley UPC - Unified Parallel C

(A joint project of LBNL and UC Berkeley)
[UCB]

Home
Downloads
Documentation
Bugs
Publications
Demos
Contact
Internal

Berkeley UPC downloads


Berkeley UPC Documentation
Berkeley UPC Site-wide
Entire Web

Latest News

April 27, 2015: Berkeley UPC 2.20.2 released!


Downloading and installing Berkeley UPC

There are the two main steps to get UPC running on your system using the Berkeley UPC Runtime. You will need to build from source, and there are several ways to do this depending on what option(s) you want for UPC translation or compilation.

  1. Optionally download and install a UPC-to-C translator or UPC compiler.
    There are several ways to get UPC running on with the Berkeley UPC Runtime. In all cases the same 'upcc' driver is used, and the resulting executables are linked to the Berkeley UPC Runtime and GASNet libraries, and can thus run over any of our supported networks, using the same 'upcrun' job spawner.
    Currently five options, encompassing four distinct translators and compilers, are supported:
    1. HTTP-based Berkeley UPC-to-C (BUPC) translator (default)
      By default, the 'upcc' compiler driver will transparently use our HTTP-based public UPC-to-C translator during compilation. This is the easiest and quickest way to install get started. You can skip directly to step 2.
    2. Locally-built Berkeley UPC-to-C (BUPC) translator
      Alternatively, you can download and install our UPC-to-C translator, and configure the UPC Runtime to use your build of the translator. This allows you to compile UPC code without being connected to the Internet, and may also result in slightly faster compilation times than the default.
    3. Locally-built GNU UPC (GUPC) compiler
      You can download and install the GNU UPC compiler. You will then configure the runtime to use your GNU UPC installation. With this configuration, the Berkeley 'upcc' compiler driver uses the GNU UPC 'gupc' compiler to compile UPC code.
    4. Locally-built Clang-based UPC-to-C (CUPC2C) translator
      You can download and install clang-upc. You will then configure the runtime to use the 'clang-upc2c' source-to-source translator from the clang-upc package. With this configuration, the Berkeley 'upcc' compiler driver uses 'clang-upc2c' to perform source-to-source translation.
    5. Locally-built Clang-UPC (CUPC) compiler
      You can download and install clang-upc. You will then configure the runtime to use the 'clang-upc' compiler from clang-upc. With this configuration, the Berkeley 'upcc' compiler driver uses 'clang-upc' to compile UPC code. This option differs from the previous one in that 'clang-upc' compiles UPC directly without source-to-source translation, and that 'clang-upc' does not support the Berkeley UPC Runtime mode with runs UPC threads as POSIX threads (pthreads).
    Additionally, one can choose to build two or more of BUPC, GUPC, CUPC2C, or CUPC and setup the 'upcc' driver to select a translator or compiler based on compile-time arguments. See the next step for more information.
  2. Download our runtime source distribution and build it following the instructions in INSTALL.TXT, which includes directions for configuring the 'upcc' driver to use any of the five options listed in the previous step.


Supported platforms

Berkeley UPC has been tested and is known to work on the following system configurations:

Platform Characteristic: Tested/supported configurations
Network Hardware / API SMP, MPI 1.1 and higher, Ethernet UDP, OpenIB InfiniBand verbs, Mellanox InfiniBand MXM API, Portals 4.x API, Cray XE/XK Gemini Cray XC30 Aries IBM PAMI (for IBM Power 775, BlueGene/Q and others), SHMEM (for SGI Altix systems)
Operating Systems Linux, FreeBSD, NetBSD, OpenBSD, Solaris, Microsoft Windows, Mac OS X, various compute-node kernels
CPU / System Architecture x86, Itanium, Opteron, Athlon, PowerPC, MIPS, SPARC v8+, Cray XD1, Cray XT series, Cray XE & XK series, Cray XC30, SGI Altix, IBM BlueBene/Q, IBM Power 775, Playstation3, ARM.
C compiler GNU GCC, Intel C, Portland Group C, SunPro C, HP C, IBM VisualAge C, Cray C, Pathscale C, LLVM Clang, Open64

Most combinations of the platforms above are supported and functional, and other unlisted platforms may work as well. See the GASNet README for the specific combinations that we've personally tested. Many of the systems listed above support both a vendor-specific C compiler and can also use gcc as the underlying C compiler - we generally recommend the vendor C compiler for performance reasons.

Note: on some of these platforms, the Berkeley UPC runtime builds, but the Berkeley UPC-to-C translator does not. When this is the case, network access to our public HTTP-based translator (or to a remote HTTP/SSH translator you set up) is needed to build UPC programs. See here for a list of platforms where the translator is known to work.

We are interested in supporting Berkeley UPC on as wide a variety of parallel systems as possible. If your system or network is not supported, and you are willing to let us use your resources for development, please contact us.


Licensing

The Berkeley UPC suite is comprised entirely of open source code. Different licenses are used for different components, however: For more information, see the LICENSE files in the source distributions.


Known bugs and limitations

A list of known bugs and limitations in the current implementation is kept in the Berkeley UPC User's Guide.


Feedback

If you encounter a bug, please go to our Bugzilla server and enter a new bug report it if the issue is not already in our database.

You may also send email to our mailing list for UPC users:

We are interested in supporting the runtime on as wide a variety of parallel systems as possible. If your system or network is not supported, and you are willing to let us use your resources for development, please contact us.

We very much appreciate your feedback.


Home
Downloads
Documentation
Bugs
Publications
Demos
Contact
Internal

This page last modified on Monday, 27-Apr-2015 16:52:04 PDT