public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/48259] New: Internal compiler errors in lto1
@ 2011-03-23 19:52 d.g.gorbachev at gmail dot com
  2011-03-23 19:52 ` [Bug lto/48259] " d.g.gorbachev at gmail dot com
                   ` (10 more replies)
  0 siblings, 11 replies; 12+ messages in thread
From: d.g.gorbachev at gmail dot com @ 2011-03-23 19:52 UTC (permalink / raw)
  To: gcc-bugs


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48259

           Summary: Internal compiler errors in lto1
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: d.g.gorbachev@gmail.com


I just experimented a bit with static libstdc++ compiled with -flto. GCC fails
with internal compiler errors when using it. (Linking with static libgcc
compiled with -flto also reveals a bug in the linker.)

Does it make sense to report such bugs? Or maybe these libraries are too
'special' and can't be expected to work this way?


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2013-04-12 20:45 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-23 19:52 [Bug lto/48259] New: Internal compiler errors in lto1 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
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

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).