public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/65274] New: Internal compiler error: should die in combat
@ 2015-03-02  9:36 linux at carewolf dot com
  2015-03-03  6:36 ` [Bug lto/65274] " maltsevm at gmail dot com
  2015-03-03 10:22 ` linux at carewolf dot com
  0 siblings, 2 replies; 3+ messages in thread
From: linux at carewolf dot com @ 2015-03-02  9:36 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65274

            Bug ID: 65274
           Summary: Internal compiler error: should die in combat
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: linux at carewolf dot com

When trying to build QtWebkit with LTO I get the internal error:
lto1: internal compiler error: in should_move_die_to_comdat, at
dwarf2out.c:6846

Note. I do not actually expect an LTO debug build of QtWebKit to succede, since
a normal debug linking step consumes 5-10Gbyte a of memory and an optimizing
link would likely consume a lot more, but I expect it to run normally and get
killed in action by the OOM killer.

Not sure I can post any meaningful intermediates here, the whole thing is
rather insane in scope. If there is anything more useful I can post please tell
me.


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

* [Bug lto/65274] Internal compiler error: should die in combat
  2015-03-02  9:36 [Bug lto/65274] New: Internal compiler error: should die in combat linux at carewolf dot com
@ 2015-03-03  6:36 ` maltsevm at gmail dot com
  2015-03-03 10:22 ` linux at carewolf dot com
  1 sibling, 0 replies; 3+ messages in thread
From: maltsevm at gmail dot com @ 2015-03-03  6:36 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65274

Mikhail Maltsev <maltsevm at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maltsevm at gmail dot com

--- Comment #1 from Mikhail Maltsev <maltsevm at gmail dot com> ---
Actually, I'm not very familiar with debug information-related stuff, but there
are two other bug reports, PR57664 and PR63505 involving ICE in the same
function - both reproduce on 4.9.x, but not on trunk.
The function used to contain an assertion (but it's on line 6837, not 6846),
https://github.com/gcc-mirror/gcc/blob/gcc-4_9_2-release/gcc/dwarf2out.c#L6837
which later became a check:
https://github.com/michaelforney/arbor/blob/11cfe14a4c9048e5b742c794a5b14bb25b08a373/packages/sys-devel/gcc/files/gcc-4.7.2-should_move_die_to_comdat.patch

Perhaps, you could try to perform the build with current version of GCC and
tell, if it still reproduces?

P.S. Nice title for bug report :).


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

* [Bug lto/65274] Internal compiler error: should die in combat
  2015-03-02  9:36 [Bug lto/65274] New: Internal compiler error: should die in combat linux at carewolf dot com
  2015-03-03  6:36 ` [Bug lto/65274] " maltsevm at gmail dot com
@ 2015-03-03 10:22 ` linux at carewolf dot com
  1 sibling, 0 replies; 3+ messages in thread
From: linux at carewolf dot com @ 2015-03-03 10:22 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65274

--- Comment #2 from Allan Jensen <linux at carewolf dot com> ---
Yes, it appears to complete the linktime compilation when using GCC trunk.


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

end of thread, other threads:[~2015-03-03 10:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-02  9:36 [Bug lto/65274] New: Internal compiler error: should die in combat linux at carewolf dot com
2015-03-03  6:36 ` [Bug lto/65274] " maltsevm at gmail dot com
2015-03-03 10:22 ` linux at carewolf 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).