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 lto/48259] Internal compiler errors in lto1
Date: Thu, 24 Mar 2011 12:41:00 -0000 [thread overview]
Message-ID: <bug-48259-4-jf1P5iTvWO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48259-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48259
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011.03.24 12:24:22
Ever Confirmed|0 |1
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-24 12:24:22 UTC ---
At least LTOing libstdc++ should work, I'm not sure about libgcc, but if
no functions of libgcc end up being used it shouldn't break.
Hm, I can't reproduce it with 4.6.
rguenther@murzim:/tmp> g++-4.6 -flto -O2 1.C 2.C 3.s
rguenther@murzim:/tmp> g++-4.6 -flto -O2 1.C 2.C 3.s -fno-use-linker-plugin
rguenther@murzim:/tmp> g++-4.6 -flto -O2 1.C 2.C 3.s -fuse-linker-plugin
rguenther@murzim:/tmp> g++-4.6 -flto -O2 1.C 2.C 3.s -flto-partition=none
rguenther@murzim:/tmp>
nor with trunk. Can you be more specific about what linker you use? Maybe
show -v output of a failing compile?
next prev parent reply other threads:[~2011-03-24 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 19:52 [Bug lto/48259] New: " d.g.gorbachev at gmail dot com
2011-03-23 19:52 ` [Bug lto/48259] " d.g.gorbachev at gmail dot com
2011-03-24 12:41 ` rguenth at gcc dot gnu.org [this message]
2011-03-26 8:29 ` d.g.gorbachev at gmail dot com
2011-03-26 9:19 ` d.g.gorbachev at gmail dot com
2011-03-26 9:20 ` d.g.gorbachev at gmail dot com
2011-03-26 9:21 ` d.g.gorbachev at gmail dot com
2011-03-27 18:28 ` d.g.gorbachev at gmail dot com
2011-08-06 23:57 ` d.g.gorbachev at gmail dot com
2011-08-21 20:34 ` d.g.gorbachev at gmail dot com
2011-12-12 21:43 ` d.g.gorbachev at gmail dot com
2013-04-12 20:45 ` d.g.gorbachev at gmail dot com
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-48259-4-jf1P5iTvWO@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).