[Chasm-interop-devel] The future of Chasm?

[<ber...@or...>]

Okay, now that I can finally post here, I can suggest we try to shift
the discussion about Chasm and standardized array interop back to this
list, where the interested parties can see it, and where it gets
archived for posterity.

To summarize recent discussions amongst CCAers about this topic:

1) Chasm has fallen behind in support for the latest compiler versions
   on a number of platforms, especially 64-bit.  This is an immediate
   issue that needs to be addressed.

2) The Babel folks need to understand whether what's been proposed for
   F2008 really covers everything they've been getting from Chasm thus
   far. (Also, I guess the previous draft stuff that some vendors have
   already implemented.)

3) Assuming the F2008 stuff is an appropriate replacement, Babel needs
   to extended to support it -- testing the compiler for support in
   autoconf, and generating the appropriate code.

4) We need for Chasm to be maintained until users upgrade to compiler
   versions supporting the F2008 features.  Just because a site has a
   compiler version that does support the needed features, doesn't
   mean the users are actually using that version.  Many sites,
   especially large centers, maintain multiple compiler versions
   simultaneously.

So I think we need to figure out an approach that covers these bases.

Are there any other major users of Chasm, besides Babel/CCA, who we
should try to draw into this discussion?
--
David E. Bernholdt                   |   Email: ber...@or... 
Oak Ridge National Laboratory        |   Phone: +1 (865) 574 3147    
http://www.csm.ornl.gov/~bernhold/   |   Fax:   +1 (865) 576 5491