[Bug libfortran/32770] -fdefault-integer-8 and the library

["fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #13 from fxcoudert at gcc dot gnu dot org  2007-07-29 11:19 -------
>From your testresults, Dominique, I see the following testcases ICE:

gfortran.dg/altreturn_5.f90
gfortran.dg/associated_2.f90
gfortran.dg/bounds_check_5.f90
gfortran.dg/char_associated_1.f90
gfortran.dg/der_array_1.f90
gfortran.dg/forall_4.f90
gfortran.dg/pointer_function_actual_1.f90
gfortran.dg/ret_pointer_1.f90
gfortran.dg/where_operator_assign_2.f90
gfortran.fortran-torture/compile/pr32417.f90
gfortran.fortran-torture/execute/intrinsic_associated.f90
gfortran.fortran-torture/execute/intrinsic_associated_2.f90
gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

We know about gfortran.fortran-torture/compile/pr32417.f90 (PR 32527, a
tree-optimization bug). My x86_64-linux with -m32 -fdefault-integer-8 revealed
the following ICES:

gfortran.dg/altreturn_5.f90
gfortran.dg/pointer_function_actual_1.f90
gfortran.fortran-torture/compile/pr32417.f90
gfortran.fortran-torture/execute/intrinsic_set_exponent.f90

So, I'm going to investigate and report altreturn_5.f90,
pointer_function_actual_1.f90 and intrinsic_set_exponent.f90. If you could
please find some time to report the other ones:

gfortran.dg/associated_2.f90
gfortran.dg/bounds_check_5.f90
gfortran.dg/char_associated_1.f90
gfortran.dg/der_array_1.f90
gfortran.dg/forall_4.f90
gfortran.dg/ret_pointer_1.f90
gfortran.dg/where_operator_assign_2.f90
gfortran.fortran-torture/execute/intrinsic_associated.f90
gfortran.fortran-torture/execute/intrinsic_associated_2.f90

I think beginning with ICEs is a worthly choice. The way to track them down is
to reduce the testcase to its bare minimum, note the exact error message and
obtain a gdb backtrace. If you need help with the latest step, we can arrange
an IRC meeting so that I can help you (send me a private mail).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32770