public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60231] [4.8/4.9 Regression] ICE on undefined generic
Date: Mon, 17 Feb 2014 09:06:00 -0000 [thread overview]
Message-ID: <bug-60231-4-WApIhJEzOA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60231-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60231
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-02-17
CC| |janus at gcc dot gnu.org
Summary|ICE on undefined generic |[4.8/4.9 Regression] ICE on
| |undefined generic
Ever confirmed|0 |1
--- Comment #1 from janus at gcc dot gnu.org ---
Confirmed. The ICE occurs with 4.8 and trunk, but 4.7 gives the following:
c0.f90:7.19:
generic :: Add => Add1, Add2
1
Error: 'add1' and 'add2' for GENERIC 'add' at (1) are ambiguous
c0.f90:5.12:
procedure :: Add1
1
Error: 'add1' must be a module procedure or an external procedure with an
explicit interface at (1)
c0.f90:6.12:
procedure :: Add2
1
Error: 'add2' must be a module procedure or an external procedure with an
explicit interface at (1)
About the first error one can argue, but the second and third one are certainly
correct. Thus the ICE is a regresssion.
next prev parent reply other threads:[~2014-02-17 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 22:16 [Bug fortran/60231] New: " antony at cosmologist dot info
2014-02-17 9:06 ` janus at gcc dot gnu.org [this message]
2014-02-17 9:20 ` [Bug fortran/60231] [4.8/4.9 Regression] " janus at gcc dot gnu.org
2014-02-17 12:31 ` janus at gcc dot gnu.org
2014-02-18 7:46 ` janus at gcc dot gnu.org
2014-02-19 7:39 ` janus at gcc dot gnu.org
2014-02-19 7:54 ` janus at gcc dot gnu.org
2014-02-19 7:55 ` janus at gcc dot gnu.org
2014-02-27 20:27 ` janus at gcc dot gnu.org
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-60231-4-WApIhJEzOA@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).