Current failures on Cygwin

[Tim Prince]

Jerry DeLisle wrote:
> Here are gfortran failures I am seeing on Cygwin as of a few hours 
> ago.  I noticed some of these are at -O3, implying some optimization 
> passes at fault. IIRC nint_2.f90 and default_format_denormal_1.f90 are 
> not new.  The rest of these are fairly recent.
>
> Maybe we need a meta-bug to track these.
>
> Regards,
>
> Jerry
>
> Running /home/Jerry/gcc/gcc44/gcc/testsuite/gfortran.dg/dg.exp ...
> FAIL: gfortran.dg/array_constructor_24.f execution test
> FAIL: gfortran.dg/array_constructor_24.f execution test
> FAIL: gfortran.dg/array_constructor_24.f execution test
> FAIL: gfortran.dg/array_constructor_24.f execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/default_format_denormal_1.f90 execution test
> FAIL: gfortran.dg/nint_2.f90 execution test
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/use_only_1.f90 (internal compiler error)
> FAIL: gfortran.dg/use_only_1.f90 (test for excess errors)
> WARNING: gfortran.dg/use_only_1.f90 compilation failed to produce 
> executable
> FAIL: gfortran.dg/g77/970915-0.f (internal compiler error)
> FAIL: gfortran.dg/g77/970915-0.f (test for excess errors)
> Running /home/Jerry/gcc/gcc44/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
> Running /home/Jerry/gcc/gcc44/gcc/testsuite/gfortran.dg/vect/vect.exp ...
> Running 
> /home/Jerry/gcc/gcc44/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp 
> ...
> Running 
> /home/Jerry/gcc/gcc44/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp 
> ...
> FAIL: gfortran.fortran-torture/execute/intrinsic_integer.f90 
> execution,  -O0
> FAIL: gfortran.fortran-torture/execute/intrinsic_integer.f90 
> execution,  -O1
> FAIL: gfortran.fortran-torture/execute/intrinsic_integer.f90 
> execution,  -O2
> FAIL: gfortran.fortran-torture/execute/intrinsic_integer.f90 
> execution,  -Os
intrinsic_integer.f90 has been failing on cygwin, powerpc, and 
i386-freebsd since 4.3.0 20080215

gfortran 4.4 still segfaults many tests at run-time when -g is set.  
Pretty good otherwise.

I verified your report of 2 new problems (new since 2 weeks ago, the 
last time I could bootstrap on cygwin):
use_only_1.f90 segfaults the compiler at all optimization levels.
array_constructor_24.f seems to get into a non-terminating loop at 
run-time, which segfaults eventually, with the problem showing up only 
at -O3.