The OpenACC specification is developed by OpenACC organization members based on the feedback provided by OpenACC users. Proposed new features to the current specification are published in Technical Reports (TR) and made available for review by users. To submit your feedback, please email to email@example.com.
Creating a new version of the specification is an iterative process that is designed not only to develop a high quality document but also collect user feedback at each step along the way. Once a technical report is approved and a new specification is close to being ratified, the Proposed Specification document is released to the user group for feedback.
The OpenACC Validation and Verification Testsuite creates unit tests to validate and verify OpenACC features and evaluates compilers' compliance to the specification. Take a look at the recent status of coverage.
- OpenACC 3.2 Specification
- OpenACC 3.1 Specification
- OpenACC 3.0 Specification
- OpenACC 2.7 Specification
- OpenACC 2.6 Specification
- OpenACC 2.6 Final Changes Document (November 2017)
- OpenACC 2.6 Public Review Draft (September 2017)
- ISC17 OpenACC 2.6 Specification Update (June 2017)
- Technical Report: Deep Copy Attach and Detach (TR-16-1)
- OpenACC 2.6 Proposed Features
- OpenACC 2.5 Specification
- Complex Data Management Tech Report (TR-14-1) Nov 2014
- OpenACC 2.0 Specification
- OpenACC 1.0 Specification