https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67118
Bug ID: 67118
Summary: gcc and gfortran started crashing recently
Product: gcc
Version: 5.2.0
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: niksah at gmail dot com
Target Milestone: ---
Created attachment 36127
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36127&action=edit
preprocessed file generated with gfortran -save-temps -c drotmg.f
gcc, gfortran and g++ started crashing on my system recently. Below, I show
the output while trying to compile one of the BLAS routines with gfortran.
gfortran -c drotmg.f
f951: internal compiler error: Illegal instruction
0xa596bf crash_signal
../../gcc-5.2.0/gcc/toplev.c:383
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.
I get similar errors with g++
0xaa39af crash_signal
../../gcc-5.2.0/gcc/toplev.c:383
and also with gcc:
0x9bd0af crash_signal
../../gcc-5.2.0/gcc/toplev.c:383
The compilers do not crash for all .f, .c, .cpp files. gcc 4.8 worked fine on
my system until at least early June but started giving the same crashes shown
above. Versions 4.8 and 5.2 of the compilers were configured/built with
default options, i.e., ../gcc.../configure, followed by make and, finally, make
install.
the exact version of GCC;
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/5.2.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-5.2.0/configure
Thread model: posix
gcc version 5.2.0 (GCC)
the system type;
$ uname -a
Linux localhost 3.10.0-229.7.2.el7.x86_64 #1 SMP Tue Jun 23 22:06:11 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
The compilers worked fine on a very similar system, which makes me suspect that
the issue is due to one of the gcc dependencies but I have been unable to
figure this out. Thanks in advance for any guidance you can provide to resolve
this issue.
