Skip to content

Milestones

List view

  • Work on OpenCoarrays 3.0 aims to produce a new application binary interface (ABI) with no references to compiler-specific descriptors. Two possibilities emerged from the May 13-15 OpenCoarrays Retreat at Dillon Beach, California, and it is likely that both will ultimately be offered was alternatives with different compilers choosing one option or another based on the compiler's intended audience and developer resources: 1. _The "Power" implementation_: an ABI that accepts Fortran 2018 C descriptors and does the heavy lifting of both managing data structures and transporting data across images. 2. _The "Sleek" implementation:_ an ABI that accepts references to memory locations that are ready for immediate transport without manipulation and potential exposes more opportunities for high-level optimizations at the cost of requiring that compiler to do more work to prepare the data for transport. Option 1 mirrors prior versions of OpenCoarrays and will be developed first because much of the existing code base can be reused and . Option 2 The plan that emerged from the Develop a c++ implementation that provides the following functions: 1. functions that require no descriptor caf_init(int argc, char* argv[]); caf_finalize(); error_stop(); num_images(); this_image(); - with no arguments sync_all(); sync_images();

    No due date
    2/2 issues closed
  • Issue #511 summarizes an important and widely useful feature that should be a high priority second only to the regression (#518) that must be fixed for the GCC 8 Support milestone. Issue #511 blocks the use of OpenCoarrays in the [Coarray ICAR] mini-app with any GCC version higher than 6.4. [Coarray ICAR]: https://bit.ly/coarray-icar-paw17

    Due by May 31, 2018
    1/1 issues closed
  • Issue #518 tracks the one regression that occurs when OpenCoarrays is built with GCC 8. When that issue has been resolved and GCC 8 has been released, we should bump the default GCC version that `install.sh` builds to 8 in order to facilitate use of the 2.0.0 support for Fortran 2018 teams, which requires GCC 8.

    Due by April 30, 2018
    2/2 issues closed
  • Due by November 18, 2017
    1/1 issues closed
  • No due date
    2/2 issues closed
  • Due by April 30, 2016
    1/1 issues closed
  • Things to be completed before the 1.2.3 release (next minor release)

    Due by January 26, 2016
    4/4 issues closed
  • This Open Coarrays major release will have new features and improvements (source to source translation)

    Due by May 1, 2017
    12/13 issues closed