This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ipa/63851] [5 Regression] ipa-icf miscompiles gfortran.dg/assumed_rank_(8|9|10).f90 at -O2 and above
- From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 17 Dec 2014 01:02:52 +0000
- Subject: [Bug ipa/63851] [5 Regression] ipa-icf miscompiles gfortran.dg/assumed_rank_(8|9|10).f90 at -O2 and above
- Auto-submitted: auto-generated
- References: <bug-63851-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63851
howarth at bromo dot med.uc.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth at bromo dot med.uc.edu
--- Comment #7 from howarth at bromo dot med.uc.edu ---
(In reply to Martin LiÅka from comment #5)
At r218792, the proposed patch reduces the fortran test suite failures on
x86_64-apple-darwin14 to just...
FAIL: gfortran.dg/assumed_rank_10.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/assumed_rank_10.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
at -m32 only which appears to backtrace as...
Program aborted. Backtrace:
#0 0x5db1
#1 0x6fcf
#2 0xbcfc7
#3 0x1a8f
#4 0x1bfa
Program received signal SIGABRT, Aborted.
0x95ed369a in __pthread_kill () from /usr/lib/system/libsystem_kernel.dylib
(gdb) bt
#0 0x95ed369a in __pthread_kill () from /usr/lib/system/libsystem_kernel.dylib
#1 0x98817f19 in pthread_kill () from /usr/lib/system/libsystem_pthread.dylib
#2 0x98c72eee in abort () from /usr/lib/system/libsystem_c.dylib
#3 0x00006fb0 in __gfortrani_sys_abort () at
../../../../gcc-5-20141216/libgfortran/runtime/error.c:180
#4 0x000bcfc8 in _gfortran_abort () at
../../../../gcc-5-20141216/libgfortran/intrinsics/abort.c:33
#5 0x00001a90 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Does this imply that we are missing a call to
compatible_types_p() somewhere that is exposed at -m32 for this particular test
case?