public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/47244] [4.6 Regression] plugin linker is used unconditionally
Date: Tue, 11 Jan 2011 13:30:00 -0000 [thread overview]
Message-ID: <bug-47244-4-iqbsD2ARxG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47244-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47244
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.01.11 13:26:42
AssignedTo|unassigned at gcc dot |hubicka at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-01-11 13:26:42 UTC ---
This change was intentional.
We will need to use linker plugin unconditionally for slim LTO support, but per
discussion with Richard, we should switch to this only for next stage1 as slim
LTO is not getting into 4.6.0.
I guess we only need to update SPECs to test -flto, should be easy.
next prev parent reply other threads:[~2011-01-11 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 16:15 [Bug driver/47244] New: " rguenth at gcc dot gnu.org
2011-01-10 16:15 ` [Bug driver/47244] " rguenth at gcc dot gnu.org
2011-01-11 13:30 ` hubicka at gcc dot gnu.org [this message]
2011-01-11 14:06 ` hubicka at gcc dot gnu.org
2011-01-11 14:07 ` dominiq at lps dot ens.fr
2011-01-11 14:09 ` Jan Hubicka
2011-01-11 14:11 ` hubicka at ucw dot cz
2011-01-11 16:48 ` hubicka at gcc dot gnu.org
2011-01-12 16:57 ` hubicka at gcc dot gnu.org
2011-01-12 17:03 ` hubicka at gcc dot gnu.org
2011-01-14 12:40 ` rguenth at gcc dot gnu.org
2011-01-14 14:49 ` rguenth 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-47244-4-iqbsD2ARxG@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).