public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/20912] C++ FE emitting assignments to read-only global symbols
Date: Thu, 14 Apr 2005 21:29:00 -0000	[thread overview]
Message-ID: <20050414212857.7230.qmail@sourceware.org> (raw)
In-Reply-To: <20050409015142.20912.dnovillo@gcc.gnu.org>


------- Additional Comments From schlie at comcast dot net  2005-04-14 21:28 -------
(In reply to comment #0)

I guess I misunderstand the problem, as given:

  const double ggPi = 3.14159265358979323846;
  double const divPi = 1 / ggPi;

It would seem that neither ggPi or divPI should be designated "unchanging"
at the tree/rtl level, as neither are global static const objects, although:

  3.14159265358979323846

is, if stored as a value; as opposed to being inlined in the code as an immediate.

ggPi and divPi are simply variables which are initialized with values at runtime;
where the fact that they're "const" has prevented an assignment (other than an
initializing one) being accepted as valid during semantic analysis.  Where post
semantic analysis, they're just variables just like any others which happen to
have no assignments specified post initialization (as enforced by the front end);
so should not be marked READONLY/unchanging to begin with, it would seem?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20912


  parent reply	other threads:[~2005-04-14 21:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09  1:52 [Bug c++/20912] New: " dnovillo at gcc dot gnu dot org
2005-04-09 12:48 ` [Bug c++/20912] " pinskia at gcc dot gnu dot org
2005-04-14 21:29 ` schlie at comcast dot net [this message]
2005-04-18 17:56 ` pinskia at gcc dot gnu dot org
2005-04-18 19:29 ` schlie at comcast dot net
2005-04-28  2:11 ` pinskia at gcc dot gnu dot org
2005-04-28  2:46 ` matz at suse dot de
2005-07-18  4:42 ` pinskia at gcc dot gnu dot org
     [not found] <bug-20912-91@http.gcc.gnu.org/bugzilla/>
2005-10-11  7:21 ` mmitchel at gcc dot gnu dot org
2005-10-11 21:06 ` mmitchel at gcc dot gnu dot org
2005-10-11 21:07 ` mmitchel at gcc dot gnu dot org
2005-10-12 14:16 ` dnovillo at redhat dot com
2005-10-12 14:55 ` mark at codesourcery dot com
2005-10-12 15:00 ` dnovillo at redhat dot com
2005-10-28 18:25 ` pinskia at gcc dot gnu dot org
2007-02-03 18:36 ` steven at gcc dot gnu dot org
2007-02-05  3:19 ` mark at codesourcery dot com
2007-02-05 22:30 ` steven at gcc dot gnu dot org
2007-02-05 22:46 ` steven at gcc dot gnu dot org
2007-02-05 22:51 ` rguenth at gcc dot gnu dot org
2007-02-05 22:51 ` rguenth at gcc dot gnu dot org
2007-02-07  0:56 ` schlie at comcast dot net
2007-05-04  0:30 ` pinskia 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=20050414212857.7230.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).