public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Fri, 30 Dec 2005 18:51:00 -0000 [thread overview]
Message-ID: <20051230185143.8127.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18918-8997@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from pinskia at gcc dot gnu dot org 2005-12-30 18:51 -------
(In reply to comment #6)
> Something to think about once F2003 support is completed. ;-)
It did not make it into F2003 but:
[13:50] < toon> pinskia: No but it still stands a chance for F2008
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2005-09-18 05:22:17 |2005-12-30 18:51:43
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18918
next parent reply other threads:[~2005-12-30 18:51 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 [this message]
2007-10-14 17:46 ` burnus at gcc dot gnu dot org
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=20051230185143.8127.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).