What is UPC, and where is it installed on XSEDE?

Unified Parallel C (UPC) is an extension of the C programming language designed for high performance computing on large-scale parallel machines. The language provides a uniform programming model for both shared and distributed memory hardware. The programmer is presented with a single shared, partitioned address space, where variables may be directly read and written by any processor, but each variable is physically associated with a single processor. UPC uses a Single Program Multiple Data (SPMD) model of computation in which the amount of parallelism is fixed at program startup time, typically with a single thread of execution per processor. For more, see the UPC project page.

To find which XSEDE resources have this software (and which version) installed, use the Comprehensive Software Search on the XSEDE Software page.

1. Make sure the first drop-down list is set to Name.
   
   
2. Enter the application name in the text box.
   
   
3. Click Search.

If your search returns 0 results, it may mean this software is not available on XSEDE. If you wish to use such an application, contact  help@xsede.org . If a product (e.g., Python) is installed on a resource, and you want to use a specific module associated with that product (e.g., Biopython), you may contact  help@xsede.org  to request its installation.

This document was developed with support from the National Science Foundation (NSF) under Grant No. 0503697 to the University of Chicago and subcontracted to Indiana University. Additional support was provided by IU through its participation in the TeraGrid, which is supported by the NSF under Grants No. 0833618, SCI451237, SCI535258, and SCI504075. 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 NSF.

This document was developed with support from National Science Foundation (NSF) grant OCI-1053575. 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 NSF.

Comments/Questions/Corrections