public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <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: Mon, 18 Apr 2005 17:56:00 -0000	[thread overview]
Message-ID: <20050418175634.18080.qmail@sourceware.org> (raw)
In-Reply-To: <20050409015142.20912.dnovillo@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-04-18 17:56 -------
Simple code which shows we now have a missed optimization:
static const double a = 1.0;
static const double b = a+1.0;

double c()
{
  return b;
}

See PR 21089.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |21089
Bug 20912 depends on bug 21089, which changed state.

Bug 21089 Summary: [4.0/4.1 Regression] C++ front-end does not "inline" the static const double
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21089

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|DUPLICATE                   |
             Status|UNCONFIRMED                 |NEWBug 20912 depends on bug 21089, which changed state.

Bug 21089 Summary: [4.0/4.1 Regression] C++ front-end does not "inline" the static const double
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21089

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|DUPLICATE                   |
             Status|UNCONFIRMED                 |NEW

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


  parent reply	other threads:[~2005-04-18 17:56 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
2005-04-18 17:56 ` pinskia at gcc dot gnu dot org [this message]
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=20050418175634.18080.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).