public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18918] Eventually support the co-array f95 extension in gfortran
Date: Sun, 14 Oct 2007 17:46:00 -0000 [thread overview]
Message-ID: <20071014174602.24295.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18918-8997@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from burnus at gcc dot gnu dot org 2007-10-14 17:46 -------
For UPC (Unified Parallel C) - the C variant of something like Co-arrays - has
been implemented for GCC 4.0.x, see: http://www.intrepid.com/upc.html
I don't know whether they have signed a contract with the FSF or whether it
helps with implementing it.
Otherwise, one can use the OpenMP backend for shared-memory systems; for
distributed memory, one could either generate MPI 2 code directly or use - as
intrepid's gcc - Berkeley's GASNet library, http://gasnet.cs.berkeley.edu/.
Regarding the status: Co-arrays are one of the few remaining bigger changes
planned for Fortran 2003; see http://www.nag.co.uk/sc22wg5/, esp. on that page:
- "Co-arrays in the next Fortran Standard"
- "Rationale for co-arrays in Fortran 2008"
- Current draft: http://www.j3-fortran.org/doc/standing/links/007.pdf
- Timetable: ftp://ftp.nag.co.uk/sc22wg5/N1651-N1700/N1693.txt
2007-12 - first working draft; 2008-04 WG5 approval of draft; 2009-07 final CD
submitted.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18918
next prev parent reply other threads:[~2007-10-14 17:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18918-8997@http.gcc.gnu.org/bugzilla/>
2005-12-30 18:51 ` pinskia at gcc dot gnu dot org
2007-10-14 17:46 ` burnus at gcc dot gnu dot org [this message]
2008-03-25 18:50 ` [Bug fortran/18918] Eventually support Fortran 2008's coarrays [co-arrays] burnus at gcc dot gnu dot org
2009-01-28 7:12 ` burnus at gcc dot gnu dot org
2009-04-29 18:16 ` burnus at gcc dot gnu dot org
2010-02-19 12:48 ` burnus at gcc dot gnu dot org
2010-04-06 16:39 ` burnus at gcc dot gnu dot org
2010-04-06 17:59 ` burnus at gcc dot gnu dot org
2010-04-06 18:16 ` burnus at gcc dot gnu dot org
2010-04-06 18:24 ` burnus at gcc dot gnu dot org
2010-04-06 19:04 ` burnus at gcc dot gnu dot org
2010-04-06 20:00 ` burnus at gcc dot gnu dot org
2010-04-09 5:55 ` burnus at gcc dot gnu dot org
2010-04-14 5:44 ` burnus at gcc dot gnu dot org
2010-04-27 8:41 ` burnus at gcc dot gnu dot org
2010-04-27 13:59 ` hjl dot tools at gmail dot com
2010-04-27 14:09 ` burnus at gcc dot gnu dot org
2010-04-28 20:43 ` burnus at gcc dot gnu dot org
2010-04-30 18:32 ` burnus at gcc dot gnu dot org
2010-05-02 15:14 ` burnus at gcc dot gnu dot org
2010-07-08 15:17 ` burnus at gcc dot gnu dot org
2004-12-10 4:18 [Bug fortran/18918] New: Eventually support the co-array f95 extension in gfortran mg_gentoo at yahoo dot com
2004-12-14 22:33 ` [Bug fortran/18918] " tobi at gcc dot gnu dot org
2004-12-15 2:56 ` mg_gentoo at yahoo dot com
2004-12-20 22:44 ` tobi at gcc dot gnu dot org
2004-12-21 9:56 ` mg_gentoo at yahoo dot com
2005-02-11 21:56 ` jblomqvi at cc dot hut dot fi
2005-06-20 7:25 ` jblomqvi at cc dot hut dot fi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071014174602.24295.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).