User account creation filtered due to spam.
Running the gcc testsuite I get the following ICE: Executing on host: /opt/devel/SCRATCH/tmp.5jnZ8G4weh/gcc-5.0.0/gcc-5.0.0/gcc/xgcc -B/opt/devel/SCRATCH/tmp.5jnZ8G4weh/gcc-5.0.0/gcc-5.0.0/gcc/ /opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -g -fcheck-pointer-bounds -mmpx -lm -o ./builtin-bnd-narrow-ptr-bounds-2-nov.exe (timeout = 300) spawn /opt/devel/SCRATCH/tmp.5jnZ8G4weh/gcc-5.0.0/gcc-5.0.0/gcc/xgcc -B/opt/devel/SCRATCH/tmp.5jnZ8G4weh/gcc-5.0.0/gcc-5.0.0/gcc/ /opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -g -fcheck-pointer-bounds -mmpx -lm -o ./builtin-bnd-narrow-ptr-bounds-2-nov.exe D:/opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c: In function 'mpx_test.chkp': D:/opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c:15:1: internal compiler error: in simplify_subreg, at simplify-rtx.c:5745 libbacktrace could not find executable to open Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. compiler exited with status 1 output is: D:/opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c: In function 'mpx_test.chkp': D:/opt/devel/gnu/src/gcc-mingw-w64/gcc-5.0.0/gcc/testsuite/gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c:15:1: internal compiler error: in simplify_subreg, at simplify-rtx.c:5745 libbacktrace could not find executable to open Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. FAIL: gcc.target/i386/mpx/builtin-bnd-narrow-ptr-bounds-2-nov.c -O3 -g (internal compiler error)
Confirmed. Backtrace: #1 0x010771df in fancy_abort ( file=file@entry=0x12d0e80 <inchash::add_rtx(rtx_def const*, inchash::hash&): :__FUNCTION__+8> "../../gcc/gcc/simplify-rtx.c", line=line@entry=5745, function=function@entry=0x12d170a <simplify_subreg(machine_mode, rtx_def*, m achine_mode, unsigned int)::__FUNCTION__> "simplify_subreg") at ../../gcc/gcc/diagnostic.c:1291 #2 0x008fa8dd in simplify_subreg (outermode=outermode@entry=BLKmode, op=op@entry=0xfff5b2c0, innermode=innermode@entry=DImode, byte=byte@entry=0) at ../../gcc/gcc/simplify-rtx.c:5745 #3 0x008fac8f in simplify_gen_subreg (outermode=BLKmode, op=0xfff5b2c0, innermode=DImode, byte=byte@entry=0) at ../../gcc/gcc/simplify-rtx.c:5967 #4 0x006ffb7f in ix86_delegitimize_address (x=<optimized out>) at ../../gcc/gcc/config/i386/i386.c:14914 #5 0x00ead454 in adjust_mems (loc=0xfff5b7f0, old_rtx=0x0, data=0xc1aa890) at ../../gcc/gcc/var-tracking.c:1057 #6 0x008fe4fc in simplify_replace_fn_rtx (x=0xfff5b7f0, old_rtx=old_rtx@entry=0x0, fn=fn@entry=0xead280 <adjust_mems(rtx, const_rtx, void*)>, data=data@entry=0xc1aa890) at ../../gcc/gcc/simplify-rtx.c:467 #7 0x008fe038 in simplify_replace_fn_rtx (x=0xfff5b800, assert happens due on call of simplify_subreg the outermode is a BLKmode. I think we should check within simplify_get_subreg for outermode == BLKmode and avoid calling of simplify_subreg for it.
As more I look as more I guess it is related to recent pic-code changes in i386.c for Darwin. I will check at what places we now assume that for PIC (especially for UNSPEC UNSPEC_PCREL) we assume that x64-code only uses path with GOT-table for PIC.
Author: tkoenig Date: Sun Mar 29 14:20:29 2015 New Revision: 221761 URL: https://gcc.gnu.org/viewcvs?rev=221761&root=gcc&view=rev Log: 2015-03-29 Thomas Koenig <tkoenig@gcc.gnu.org> PR libgfortran/65564 * gfortran.dg/open_errors_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/open_errors_2.f90 Modified: trunk/gcc/testsuite/ChangeLog
Of course, the commit had nothing to do with this PR.
No primary/secondary target in the list of affected targets.
GCC 5.1 has been released.
GCC 5.2 is being released, adjusting target milestone to 5.3.
GCC 5.3 is being released, adjusting target milestone.
GCC 5.4 is being released, adjusting target milestone.