public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47399] [OOP] ICE with TBP of a PARAMETER
Date: Sat, 28 Jan 2012 21:00:00 -0000 [thread overview]
Message-ID: <bug-47399-4-T2fsY0m95t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47399-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47399
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-01-28
Ever Confirmed|0 |1
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-28 20:33:33 UTC ---
> TODO: Check whether we now allow invalid code. Check the c.l.f thread.
I have had a look at the thread, and it seems that NAG is complaining for the
test in comment #0. For those who have access to it (and other compilers), is
it still true?
Note that the test and some avatars compile with -std=f2003.
next prev parent reply other threads:[~2012-01-28 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 15:19 [Bug fortran/47399] New: " burnus at gcc dot gnu.org
2011-01-21 21:36 ` [Bug fortran/47399] " burnus at gcc dot gnu.org
2011-01-22 0:41 ` [Bug fortran/47399] [OOP] " burnus at gcc dot gnu.org
2011-01-22 14:24 ` burnus at gcc dot gnu.org
2011-01-22 21:25 ` burnus at gcc dot gnu.org
2011-12-12 8:10 ` burnus at gcc dot gnu.org
2012-01-28 21:00 ` dominiq at lps dot ens.fr [this message]
2013-09-01 14:38 ` dominiq at lps dot ens.fr
2013-12-14 20:17 ` dominiq at lps dot ens.fr
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=bug-47399-4-T2fsY0m95t@http.gcc.gnu.org/bugzilla/ \
--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).