[Bug bootstrap/64102] New: ARM bootstrap fails with segfault with -mapcs in BOOT_CFLAGS
ktkachov at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Fri Nov 28 13:55:00 GMT 2014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64102
Bug ID: 64102
Summary: ARM bootstrap fails with segfault with -mapcs in
BOOT_CFLAGS
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
I'm seeing a bootstrap segfault in stage2 on arm-none-linux-gnueabihf when
given BOOT_CFLAGS="-O2 -mapcs":
$BUILD/./gcc/xgcc -B$BUILD/./gcc/ -B$BUILD/armv7l-unknown-linux-gnueabihf/bin/
-B$BUILD/armv7l-unknown-linux-gnueabihf/lib/ -isystem
$BUILD/armv7l-unknown-linux-gnueabihf/include -isystem
$BUILD/armv7l-unknown-linux-gnueabihf/sys-include -g -O2 -O2 -g -O2
-DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -fPIC -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fPIC -fno-inline -I. -I. -I../.././gcc -I$SRC/libgcc
-I$SRC/libgcc/. -I$SRC/libgcc/../gcc -I$SRC/libgcc/../include -DHAVE_CC_TLS
-o _eprintf.o -MT _eprintf.o -MD -MP -MF _eprintf.dep -DL_eprintf -c
$SRC/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
$SRC/libgcc/libgcc2.c: In function '__eprintf':
$SRC/libgcc/libgcc2.c:2114:3: internal compiler error: Segmentation fault
fprintf (stderr, string, expression, line, filename);
^
0x69c0cf crash_signal
$SRC/gcc/toplev.c:359
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
(kyrtka01@pdtl-cb1)~/builds/gcc-bootstrap-apcs-clean/
This is based on r218090 with configuration:
--with-float=hard --with-cpu=cortex-a15 --with-mode=arm --with-fpu=neon-vfpv4
--enable-languages=c,c++,fortran
Bootstrap without -mapcs works fine.
I don't know if this is a regression, didn't try released compilers.
Can someone please confirm this?
More information about the Gcc-bugs
mailing list