------- Comment #2 from kmccarty at debian dot org 2008-03-21 17:06 ------- Hi gfortran developers,
I can confirm that this ICE still happens on arm with gfortran 4.3 rc2 [*], and with the optimization reduced to -O2 (-funroll-loops -O1 is OK, as is -O3 without -funroll-loops). [*] This is on a machine that I don't administer so unfortunately I cannot test with the very latest gfortran. (sid)[EMAIL PROTECTED]:~$ gfortran-4.3 -v Using built-in specs. Target: arm-linux-gnu Configured with: ../src/configure linux gnu Thread model: posix gcc version 4.3.0 20080301 (prerelease) [gcc-4_3-branch revision 132801] (Debian 4.3.0~rc2-1) (sid)[EMAIL PROTECTED]:~$ gfortran-4.3 -funroll-loops -O2 -c seispack.f seispack.f: In function 'invit': seispack.f:1742: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions. I have also observed a similar ICE, which could very well be the same bug, with a smaller FORTRAN file "ranecu.F" that may be easier to run tests on. In that case the ICE occurs with -funroll-loops and with optimization as low as -O1. That ICE I have reported in Debian's BTS at http://bugs.debian.org/466791 -- and I prepared a simple test case for it at http://people.debian.org/~kmccarty/arm-ICE-test.tar.gz . (The .f and .s files in that tarball were generated by gfortran from svn 20080202, Debian package version 4.3-20080202-1, but since the ICE still occurs I'm guessing this doesn't matter so much, and you can easily regenerate them with the Makefile in the test case tarball.) best regards, Kevin McCarty -- kmccarty at debian dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kmccarty at debian dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35079 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
