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/59720] [OOP] class/extends, multiple generic assignment
Date: Wed, 08 Jan 2014 20:56:00 -0000 [thread overview]
Message-ID: <bug-59720-4-qPOBVp8Ufp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59720-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59720
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from janus at gcc dot gnu.org ---
(In reply to Harald Anlauf from comment #9)
> > Could you also check what XLF and NAG report on comment 1 (which is a
> > somewhat more questionable case)?
>
> Apparently both agree with gfortran ;-)
... and with my interpretation of the standard in comment 5. Great. Thanks a
lot!
Paul, I think you should rather report the bug with Intel. I'm closing this PR
as invalid. Thanks for reporting the difference in behavior, nevertheless!
prev parent reply other threads:[~2014-01-08 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 12:57 [Bug fortran/59720] New: Re: f2003/f2008, class/extends, multiple gemeric assignment kapinos at rz dot rwth-aachen.de
2014-01-08 14:14 ` [Bug fortran/59720] " dominiq at lps dot ens.fr
2014-01-08 14:55 ` [Bug fortran/59720] [OOP] " janus at gcc dot gnu.org
2014-01-08 15:55 ` [Bug fortran/59720] [OOP] class/extends, multiple generic assignment janus at gcc dot gnu.org
2014-01-08 16:34 ` janus at gcc dot gnu.org
2014-01-08 17:03 ` janus at gcc dot gnu.org
2014-01-08 17:15 ` janus at gcc dot gnu.org
2014-01-08 18:42 ` janus at gcc dot gnu.org
2014-01-08 19:28 ` anlauf at gmx dot de
2014-01-08 19:38 ` janus at gcc dot gnu.org
2014-01-08 20:56 ` janus at gcc dot gnu.org [this message]
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-59720-4-qPOBVp8Ufp@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).