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/44925] [OOP] C_LOC with CLASS pointer
Date: Tue, 13 Jul 2010 11:52:00 -0000 [thread overview]
Message-ID: <20100713115233.7672.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44925-17721@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from burnus at gcc dot gnu dot org 2010-07-13 11:52 -------
For the program in comment 0, NAG prints:
Error: aaa.f90, line 16: The argument to C_LOC must not be polymorphic
though ifort and crayftn accept the code. Thus, at least with
-std=f95/f2003/f2008 one should reject it. Whether one wants to allow it as
extension (-std=gnu) is another question. It can be useful, sometimes, even
though it is not well defined.
(In reply to comment #2)
> (In reply to comment #1)
> > However, it regresses at least on c_loc_tests_5.f03 and c_loc_tests_14.f90.
>
> Actually I have the feeling that both of these test cases are invalid, and the
> patch is right to reject them.
Well, NAG, ifort, pgi, and crayftn compile both programs; g95 compiles at least
c_loc_tests_5.f03; thus, I am inclined to say that those two tests are valid.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44925
next prev parent reply other threads:[~2010-07-13 11:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 20:52 [Bug fortran/44925] New: [OOP] CLASS pointer reported unassociated to C_LOC barron dot bichon at swri dot org
2010-07-12 21:10 ` [Bug fortran/44925] [OOP] C_LOC with CLASS pointer janus at gcc dot gnu dot org
2010-07-13 9:45 ` janus at gcc dot gnu dot org
2010-07-13 11:11 ` janus at gcc dot gnu dot org
2010-07-13 11:52 ` burnus at gcc dot gnu dot org [this message]
2010-07-13 12:04 ` burnus at gcc dot gnu dot org
2010-07-13 12:13 ` janus at gcc dot gnu dot org
2010-07-13 12:32 ` janus at gcc dot gnu dot org
2010-07-13 13:54 ` janus at gcc dot gnu dot org
2010-07-13 15:54 ` burnus at gcc dot gnu dot org
2010-07-14 8:09 ` janus at gcc dot gnu dot org
2010-07-14 8:16 ` janus at gcc dot gnu dot 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=20100713115233.7672.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).