The first one is: Executing on host: /mnt/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/ mnt/gnu/gcc/objdir/gcc/testsuite/gfortran/../../ /mnt/gnu/gcc/gcc/gcc/testsuite/ gfortran.dg/actual_array_constructor_2.f90 -O0 -pedantic-errors -L/mnt/gnu/ gcc/objdir/hppa2.0w-hp-hpux11.11/./libgfortran/.libs -L/mnt/gnu/gcc/objdir/hppa2 .0w-hp-hpux11.11/./libgfortran/.libs -L/mnt/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11 /./libiberty -lm -o ./actual_array_constructor_2.exe (timeout = 300) /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/actual_array_constructor_2.f90: In fu nction 'MAIN__': /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/actual_array_constructor_2.f90:22: in ternal compiler error: in emit_move_insn, at expr.c:3304 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. compiler exited with status 1 output is: /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/actual_array_constructor_2.f90: In fu nction 'MAIN__': /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/actual_array_constructor_2.f90:22: in ternal compiler error: in emit_move_insn, at expr.c:3304 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. FAIL: gfortran.dg/actual_array_constructor_2.f90 -O0 (internal compiler error) FAIL: gfortran.dg/actual_array_constructor_2.f90 -O0 (test for excess errors) Excess errors: /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/actual_array_constructor_2.f90:22: in ternal compiler error: in emit_move_insn, at expr.c:3304 WARNING: gfortran.dg/actual_array_constructor_2.f90 -O0 compilation failed to produce executable It looks like the following change is the likely cause of this regression: 2008-02-02 Richard Henderson <rth@redhat.com> PR c/34993 * tree.c (build_type_attribute_qual_variant): Skip TYPE_DOMAIN for unbounded arrays.
Subject: Re: [4.2 Regression] 841 unexpected failures in gfortran testsuite > CC| |rth at gcc dot gnu dot org I'm sorry but Richard's change isn't the cause. There's only one other change since the 4.2.3 release that could be the cause, but I better confirm that it actually introduced the the regression. Dave
It turns out these failures are a result of using the 2.0n ABI with gmp-4.2.2. This is the default for hppa2.0w-hp-hpux11.11. In all my previous testing, I had built GMP using the standard 1.x ABI. Using the 2.0n ABI affects libmpfr. The 2.0n ABI attempts to exploit the 64-bit registers and instructions present in PA-RISC 2.0 when using the 32-bit HP-UX runtime. This is possible because wide HP-UX kernels maintain a full 64-bit context for 32-bit applications. I expect this problem affects all GCC versions requiring GMP for this target.
4.2.4 is being released, changing milestones to 4.2.5.
Regression marker was removed, removing milestone.
Do you know if these work after the fixes you did recently?
On 2/1/2012 3:20 PM, pinskia at gcc dot gnu.org wrote: > Do you know if these work after the fixes you did recently? Unlikely, however, I should recheck the report and try to find the problem.