public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mueller at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31809] [4.1 Regression] sometimes TREE_READONLY is still set for non read only variables causing wrong code
Date: Wed, 20 Jun 2007 16:27:00 -0000 [thread overview]
Message-ID: <20070620162740.28990.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31809-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from mueller at gcc dot gnu dot org 2007-06-20 16:27 -------
Subject: Bug 31809
Author: mueller
Date: Wed Jun 20 16:27:23 2007
New Revision: 125887
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=125887
Log:
2007-06-20 Dirk Mueller <dmueller@suse.de>
PR c++/31809
PR c++/31806
Backport from mainline:
2007-05-31 Jakub Jelinek <jakub@redhat.com>
* decl.c (cp_finish_decl): Also clear was_readonly if a static var
needs runtime initialization.
2007-05-30 Jakub Jelinek <jakub@redhat.com>
* decl.c (cp_finish_decl): Clear TREE_READONLY flag on TREE_STATIC
variables that need runtime initialization.
* g++.dg/opt/static5.C: New testcase
* g++.dg/opt/static6.C: Likewise
Added:
branches/gcc-4_1-branch/gcc/testsuite/g++.dg/opt/static5.C
branches/gcc-4_1-branch/gcc/testsuite/g++.dg/opt/static6.C
Modified:
branches/gcc-4_1-branch/gcc/cp/ChangeLog
branches/gcc-4_1-branch/gcc/cp/decl.c
branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31809
next prev parent reply other threads:[~2007-06-20 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 0:25 [Bug c++/31809] New: [4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2007-05-04 0:26 ` [Bug c++/31809] " pinskia at gcc dot gnu dot org
2007-05-04 9:33 ` rguenth at gcc dot gnu dot org
2007-05-11 20:02 ` mmitchel at gcc dot gnu dot org
2007-05-25 11:39 ` jakub at gcc dot gnu dot org
2007-05-28 1:12 ` mmitchel at gcc dot gnu dot org
2007-05-30 17:58 ` jakub at gcc dot gnu dot org
2007-05-30 21:24 ` jakub at gcc dot gnu dot org
2007-05-30 22:46 ` mueller at gcc dot gnu dot org
2007-05-30 23:03 ` mark at codesourcery dot com
2007-05-31 9:06 ` mueller at gcc dot gnu dot org
2007-05-31 10:01 ` jakub at gcc dot gnu dot org
2007-05-31 16:33 ` mark at codesourcery dot com
2007-06-08 21:49 ` [Bug c++/31809] [4.1/4.2 " mueller at gcc dot gnu dot org
2007-06-20 16:27 ` mueller at gcc dot gnu dot org [this message]
2007-06-20 16:28 ` [Bug c++/31809] [4.1 " mueller 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=20070620162740.28990.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).