public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <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: Wed, 12 Oct 2005 14:55:00 -0000 [thread overview]
Message-ID: <20051012145544.5740.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20912-91@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from mark at codesourcery dot com 2005-10-12 14:55 -------
Subject: Re: C++ FE emitting assignments to read-only global
symbols
dnovillo at redhat dot com wrote:
> Thanks Mark. The underlying code has shifted in the interim. There was
> another bug that would cause us to ICE with code that specifically casted
> away constness. We now should get this micro-optimization on the cases we
> cared for (call-clobbering situations, mostly).
OK, so my patch is no longer directly useful then? (It still seems like
it would be an improvement in the abstract, in that assigning to
TREE_READONLY variables is evil, but if it won't have any immediate
tangible benefit, I'll leave this for 4.2.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20912
next prev parent reply other threads:[~2005-10-12 14:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
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
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=20051012145544.5740.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).