Difference between revisions of "OpenACC"
From HPC users
Jump to navigationJump to search
| Line 5: | Line 5: | ||
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 ([http://www.openacc.org/sites/default/files/OpenACC%202%200.pdf see here for more information]]. Like OpenMP 4.0 and newer, code can be started on both the CPU and GPU. | 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 ([http://www.openacc.org/sites/default/files/OpenACC%202%200.pdf see here for more information]]. Like OpenMP 4.0 and newer, code can be started on both the CPU and GPU. | ||
Support of OpenACC is available in commercial compilers from [[PGI]]. Tutorials and documantation can be found on http://www.openacc.org/. | Support of OpenACC is available in commercial compilers from [[PGI Compiler|PGI]]. Tutorials and documantation can be found on http://www.openacc.org/. | ||
Revision as of 13:30, 27 March 2017
Introduction
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. [1]
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 (see here for more information]. Like OpenMP 4.0 and newer, code can be started on both the CPU and GPU.
Support of OpenACC is available in commercial compilers from PGI. Tutorials and documantation can be found on http://www.openacc.org/.
