public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51308] PARAMETER attribute conflicts with SAVE attribute
Date: Mon, 28 Nov 2011 14:22:00 -0000 [thread overview]
Message-ID: <bug-51308-4-esOQPY3MLU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51308-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51308
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-11-28 13:58:02 UTC ---
On Mon, Nov 28, 2011 at 07:51:02AM +0000, burnus at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51308
>
> --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-28 07:51:02 UTC ---
> (In reply to comment #2)
> > - conf2 (is_bind_c);
> > + if (!(name && (strcmp(name, "c_null_ptr") == 0 || strcmp(name,
> > "c_null_funptr") == 0)))
> > + conf2 (is_bind_c);
>
> I think one should use "if (!is_iso_c)". And why do you keep the save
> attribute? I think the following should work as well.
I kept the SAVE attribute because the comment (which you remove
in your patch) claims that it is needed to actually allow the
the compiler to initialize c_null_ptr and c_null_funptr to NULL.
I did not go through the code to validate the comment's claim.
I did not use is_iso_c because I forgot about its existence.
If your patch passes regression testing, go ahead and commit it.
next prev parent reply other threads:[~2011-11-28 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 9:24 [Bug fortran/51308] New: " matthias.moeller at math dot tu-dortmund.de
2011-11-26 20:50 ` [Bug fortran/51308] " kargl at gcc dot gnu.org
2011-11-27 22:14 ` sgk at troutmask dot apl.washington.edu
2011-11-28 9:35 ` burnus at gcc dot gnu.org
2011-11-28 14:22 ` sgk at troutmask dot apl.washington.edu [this message]
2011-11-28 14:24 ` burnus at gcc dot gnu.org
2011-11-28 14:28 ` burnus at gcc dot gnu.org
2011-11-28 14:38 ` burnus at gcc dot gnu.org
2011-11-28 15:17 ` 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-51308-4-esOQPY3MLU@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).