public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52188] [4.7 regression] IPA-CP change broke libstdc++ symbol versioning on Solaris
Date: Fri, 10 Feb 2012 11:32:00 -0000 [thread overview]
Message-ID: <bug-52188-4-80YNl0ZdxJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52188-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52188
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-10
Ever Confirmed|0 |1
--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-10 11:31:00 UTC ---
So, if we'd want to be really consistent with symbols remaining in the
libstdc++ object files at different optimization levels (I guess if you
build libstdc++ with -O3 things might be different again) then we need
to avoid removing unused instantiated templates as part of the optimization
process. Not sure on what basis we choose to be exported symbols right now.
next prev parent reply other threads:[~2012-02-10 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:30 [Bug tree-optimization/52188] New: " ro at gcc dot gnu.org
2012-02-09 18:32 ` [Bug tree-optimization/52188] " ro at gcc dot gnu.org
2012-02-09 18:33 ` ro at gcc dot gnu.org
2012-02-09 18:34 ` ro at gcc dot gnu.org
2012-02-09 18:34 ` ro at gcc dot gnu.org
2012-02-10 10:25 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-10 11:24 ` rguenth at gcc dot gnu.org
2012-02-10 11:32 ` rguenth at gcc dot gnu.org [this message]
2012-02-10 12:31 ` jakub at gcc dot gnu.org
2012-02-16 16:10 ` jamborm at gcc dot gnu.org
2012-02-16 20:06 ` [Bug libstdc++/52188] " ro at gcc dot gnu.org
2012-02-16 20:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-16 20:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-16 20:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-20 11:46 ` rguenth at gcc dot gnu.org
2012-02-20 13:25 ` jamborm at gcc dot gnu.org
2012-02-27 13:55 ` ro at gcc dot gnu.org
2012-02-27 14:13 ` ro 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-52188-4-80YNl0ZdxJ@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).