|Stable release||2.0 / June 2013|
|Written in||C, C++, and Fortran|
OpenACC (for Open Accelerators) is a programming standard for parallel computing developed by Cray, CAPS, Nvidia and PGI. The standard is designed to simplify parallel programming of heterogeneous CPU/GPU systems.
Like in OpenMP, the programmer can annotate C, C++ and Fortran source code to identify the areas that should be accelerated using compiler directives and additional functions. Like OpenMP 4.0 and newer, code can be started on both the CPU and GPU.
OpenACC members have worked as members of the OpenMP standard group to merge into OpenMP specification to create a common specification which extends OpenMP to support accelerators in a future release of OpenMP. These efforts resulted in a technical report for comment and discussion timed to include the annual Supercomputing Conference (November 2012, Salt Lake City) and to address non-Nvidia accelerator support with input from hardware vendors who participate in OpenMP.
In November 12, 2012, at the SC12 conference, a draft of the OpenACC version 2.0 specification was presented. New suggested capabilities include new controls over data movement (such as better handling of unstructured data and improvements in support for non-contiguous memory), and support for explicit function calls and separate compilation (allowing the creation and reuse of libraries of accelerated code).
The OpenARC compiler is an open source, C language compiler developed over the past several years at Oak Ridge National Laboratory to fully support all features in the OpenACC 1.0 specification. An experimental open source compiler, accULL, is developed by the University of La Laguna (C language only).
GCC support for OpenACC was slow in coming. A GPU-targeting implementation from Samsung was announced in September 2013; this translated OpenACC 1.1-annotated code to OpenCL. The announcement of a "real" implementation followed two months later, this time from NVIDIA and based on OpenACC 2.0. This sparked some controversy, as the implementation would only target NVIDIA's own PTX assembly language, for which no open source assembler or runtime was available. Experimental support for OpenACC/PTX did end up in GCC as of version 5.1.
In a way similar to OpenMP 3.x on homogeneous system or the earlier OpenHMPP, the primary mode of programming in OpenACC is directives. The specifications also include a runtime library defining several support functions. To exploit them, user should include "openacc.h" in C or "openacc_lib.h" in Fortran; and then call acc_init() function.
OpenACC defines an extensive list of pragmas (directives), for example:
#pragma acc parallel #pragma acc kernels
#pragma acc data
Is the main directive to define and copy data to and from the accelerator.
#pragma acc loop
Is used to define the type of parallelism in a
#pragma acc cache #pragma acc update #pragma acc declare #pragma acc wait
There are some runtime API functions defined too: acc_get_num_devices(), acc_set_device_type(), acc_get_device_type(), acc_set_device_num(), acc_get_device_num(), acc_async_test(), acc_async_test_all(), acc_async_wait(), acc_async_wait_all(), acc_init(), acc_shutdown(), acc_on_device(), acc_malloc(), acc_free().
OpenACC generally takes care of work organisation for the target device however this can be overridden through the use of gangs and workers. A gang consists of workers and operates over a number of processing elements (as with a workgroup in OpenCL).
- "Nvidia, Cray, PGI, and CAPS launch ‘OpenACC’ programming standard for parallel computing". The Inquirer. 4 November 2011.
- "OpenACC standard version 2.0" (PDF). OpenACC.org. Retrieved 14 January 2014.
- "How does the OpenACC API relate to the OpenMP API?". OpenACC.org. Retrieved 14 January 2014.
- "How did the OpenACC specifications originate?". OpenACC.org. Retrieved 14 January 2014.
- "The OpenMP Consortium Releases First Technical Report". OpenMP.org. 5 November 2012. Retrieved 14 January 2014.
- "OpenMP at SC12". OpenMP.org. 29 August 2012. Retrieved 14 January 2014.
- "OpenACC Group Reports Expanding Support for Accelerator Programming Standard". HPCwire. 20 June 2012. Retrieved 14 January 2014.
- "OpenACC Version 2.0 Posted for Comment". OpenACC.org. 12 November 2012. Retrieved 14 January 2014.
- "OpenACC Standard to Help Developers to Take Advantage of GPU Compute Accelerators". Xbit laboratories. 16 November 2011. Retrieved 14 January 2014.
- "CAPS Announcing Full Support for OpenACC 2.0 in its Compilers". HPCwire. 14 November 2013. Retrieved 14 January 2014.
- "OpenUH Compiler". Retrieved 4 March 2014.}
- "OpenARC Compiler". Retrieved 4 November 2014.
- Larabel, Michael (30 September 2013). "GCC Support Published For OpenACC On The GPU". Phoronix.
- "accULL The OpenACC research implementation". Retrieved 14 January 2014.
- Larabel, Michael (4 December 2012). "OpenACC Still Not Loved By Open Compilers". Phoronix.
- Larabel, Michael (14 November 2013). "OpenACC 2.0 With GPU Support Coming To GCC". Phoronix.
- Larabel, Michael (15 November 2013). "NVIDIA, Mentor Graphics May Harm GCC". Phoronix.
- Larabel, Michael (21 November 2013). "In-Fighting Continues Over OpenACC In GCC". Phoronix.
- Schwinge, Thomas (15 January 2015). "Merge current set of OpenACC changes from gomp-4_0-branch". gcc (Mailing list). Retrieved 15 January 2015.
- "Easy GPU Parallelism with OpenACC". Dr.Dobb's. 11 June 2012. Retrieved 14 January 2014.
- "OpenACC API QuickReference Card, version 1.0" (PDF). NVidia. November 2011. Retrieved 14 January 2014.
- "OpenACC Kernels and Parallel Constructs". PGI insider. August 2012. Retrieved 14 January 2014.
- "OpenACC parallel section VS kernels". CAPS entreprise Knowledge Base. 3 January 2013. Retrieved 14 January 2014.