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/47023] [4.6/4.7 regression] C_Sizeof: Rejects valid code
Date: Sun, 16 Oct 2011 08:44:00 -0000 [thread overview]
Message-ID: <bug-47023-4-j28QIGoHGC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47023-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47023
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011-10-16
AssignedTo|unassigned at gcc dot |janus at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #10 from janus at gcc dot gnu.org 2011-10-16 08:43:56 UTC ---
(In reply to comment #9)
> > This patch itself doesn't do anything wrong AFAICS, it rather seems to expose
> > an underlying bug: Either we need to set the 'is_c_interop' flag correctly or
> > loosen the checks in verify_c_interop.
>
> I think the latter. I think one can allow all intrinsic types.
On second thought, I'm not so sure about this. Is this actually allowed by the
Fortran standard? (If not, one could think about allowing it only with
--std=gnu as an extension.)
> Note, additionally, that setting attr.is_c_interop is kind of difficult for
> 0.0_c_int ...
Well, no. We don't need to set 'attr.is_c_interop', but 'ts.is_c_interop',
which can also be done for constants. I'm right now testing a patch which does
so and fixes the regression.
next prev parent reply other threads:[~2011-10-16 8:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 8:59 [Bug fortran/47023] New: " burnus at gcc dot gnu.org
2010-12-22 10:28 ` [Bug fortran/47023] " burnus at gcc dot gnu.org
2011-09-20 11:47 ` florian.rathgeber at gmail dot com
2011-09-20 15:36 ` [Bug fortran/47023] [4.6/4.7 regression] " kargl at gcc dot gnu.org
2011-09-20 15:40 ` kargl at gcc dot gnu.org
2011-09-20 16:49 ` dominiq at lps dot ens.fr
2011-09-29 13:12 ` burnus at gcc dot gnu.org
2011-09-29 13:20 ` rguenth at gcc dot gnu.org
2011-09-29 13:21 ` burnus at gcc dot gnu.org
2011-09-29 13:29 ` janus at gcc dot gnu.org
2011-09-29 15:52 ` burnus at gcc dot gnu.org
2011-10-16 8:44 ` janus at gcc dot gnu.org [this message]
2011-10-16 19:43 ` janus at gcc dot gnu.org
2011-10-17 9:47 ` janus at gcc dot gnu.org
2011-10-17 16:00 ` janus at gcc dot gnu.org
2011-10-17 16:16 ` [Bug fortran/47023] " janus at gcc dot gnu.org
2011-10-17 19:11 ` janus at gcc dot gnu.org
2011-10-17 19:23 ` janus at gcc dot gnu.org
2011-10-18 10:48 ` janus at gcc dot gnu.org
2011-10-18 11:07 ` janus at gcc dot gnu.org
2011-10-18 12:04 ` janus at gcc dot gnu.org
2011-10-18 12:18 ` janus at gcc dot gnu.org
2011-10-18 12:20 ` janus at gcc dot gnu.org
2011-10-18 12:48 ` burnus at gcc dot gnu.org
2011-10-18 13:46 ` janus at gcc dot gnu.org
2011-10-19 22:08 ` janus at gcc dot gnu.org
2011-10-19 22:10 ` janus at gcc dot gnu.org
2013-03-25 15:53 ` burnus at gcc dot gnu.org
2013-03-25 17:46 ` burnus 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-47023-4-j28QIGoHGC@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).