public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <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:24:00 -0000	[thread overview]
Message-ID: <bug-51308-4-IT23eB8ttT@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 #5 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-28 14:17:50 UTC ---
(In reply to comment #4)
> 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.

Well, an initialization (sym->value) can only be only used for PARAMETERs or
for variables in static memory ("SAVE"). Having both "SAVE" and "PARAMETER"
does not really make sense. I assume that first the SAVE was added - and only
later PARAMETER (with a similar comment and many lines later in the file).

I have submitted the patch for approval at
  http://gcc.gnu.org/ml/fortran/2011-11/msg00234.html
and given your approval in comment 4 I will commit it. Thanks for looking
through my patch and for debugging and creating the draft patch of comment 2.


  parent reply	other threads:[~2011-11-28 14:18 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
2011-11-28 14:24 ` burnus at gcc dot gnu.org [this message]
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-IT23eB8ttT@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).