public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/48065] New: LTO: assertion failed in optimize_inline_calls, at tree-inline.c:4246
@ 2011-03-10 20:00 d.g.gorbachev at gmail dot com
  2011-03-10 20:00 ` [Bug lto/48065] " 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-10 20:00 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: LTO: assertion failed in optimize_inline_calls, at
                    tree-inline.c:4246
           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


Created attachment 23618
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23618
testcase

In file included from :0:0:
main.c: In function 'main':
main.c:3:5: internal compiler error: in optimize_inline_calls, at
tree-inline.c:4246


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

end of thread, other threads:[~2020-04-14  6:20 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-10 20:00 [Bug lto/48065] New: LTO: assertion failed in optimize_inline_calls, at tree-inline.c:4246 d.g.gorbachev at gmail dot com
2011-03-10 20:00 ` [Bug lto/48065] " d.g.gorbachev at gmail dot com
2011-03-11 10:03 ` rguenth at gcc dot gnu.org
2011-07-14 23:16 ` d.g.gorbachev at gmail dot com
2011-07-15  0:02 ` d.g.gorbachev at gmail dot com
2013-01-03 16:34 ` hubicka at gcc dot gnu.org
2013-01-03 16:37 ` hubicka at gcc dot gnu.org
2013-01-03 16:41 ` rguenth at gcc dot gnu.org
2013-01-04 10:51 ` rguenth at gcc dot gnu.org
2013-01-04 21:26 ` hubicka at ucw dot cz
2020-04-13 18:41 ` asolokha at gmx dot com
2020-04-14  6:20 ` rguenth at gcc dot gnu.org

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