Bug 56927 - 4.7.2 build ICEs when built with 4.8.0 and --disable-bootstrap
Summary: 4.7.2 build ICEs when built with 4.8.0 and --disable-bootstrap
Alias: None
Product: gcc
Classification: Unclassified
Component: bootstrap (show other bugs)
Version: unknown
: P3 normal
Target Milestone: 4.7.3
Assignee: Not yet assigned to anyone
Depends on:
Reported: 2013-04-11 19:17 UTC by Segher Boessenkool
Modified: 2013-04-12 00:31 UTC (History)
1 user (show)

See Also:
Host: x86_64-linux
Target: x86_64-linux
Build: x86_64-linux
Known to work:
Known to fail:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Segher Boessenkool 2013-04-11 19:17:26 UTC
When using a 4.8.0 host compiler and configuring with --disable-bootstrap,
a build of 4.7.2 fails with

/home/segher/src/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2':
/home/segher/src/gcc-4.7.2/libgcc/libgcc2.c:273:1: internal compiler error: Segmentation fault

There is no such error if the host compiler is 4.4 or 4.7, or without
--disable-bootstrap; it does have the error if doing a cross to i386-elf.
I haven't tested with tip-of-tree of either 4.7 or 4.8 or on different
Comment 1 Segher Boessenkool 2013-04-11 19:25:05 UTC
Forgot to mention...  I debugged this a little; it happens during
the build of the 32-bit libgcc, and gdb says

Program received signal SIGSEGV, Segmentation fault.
build_conflict_bit_table ()
    at /home/segher/src/gcc-4.7.2/gcc/ira-conflicts.c:178
178                   ira_allocno_t live_a = OBJECT_ALLOCNO (live_obj);
(gdb) bt
#0  build_conflict_bit_table ()
    at /home/segher/src/gcc-4.7.2/gcc/ira-conflicts.c:178
#1  ira_build_conflicts ()
    at /home/segher/src/gcc-4.7.2/gcc/ira-conflicts.c:856
#2  0x000000000067eccf in ira_build ()
    at /home/segher/src/gcc-4.7.2/gcc/ira-build.c:3101
#3  0x0000000000679177 in ira (f=<optimized out>)
    at /home/segher/src/gcc-4.7.2/gcc/ira.c:3626
#4  rest_of_handle_ira () at /home/segher/src/gcc-4.7.2/gcc/ira.c:3798

(gdb) p live_obj
$1 = (ira_object_t) 0x0
Comment 2 Jakub Jelinek 2013-04-11 20:02:43 UTC
You should use 4.7.3 instead, or at least make sure to have
http://gcc.gnu.org/r191605 applied.
Comment 3 Segher Boessenkool 2013-04-12 00:15:26 UTC
Hey, 4.7.3 didn't exist yet :-)

Confirmed fixed.
Comment 4 Andrew Pinski 2013-04-12 00:31:08 UTC
(In reply to comment #3)
> Hey, 4.7.3 didn't exist yet :-)

It was released today.