Many failures in the test suite with -fdefault-integer-8 come from tests mixing
C and Fortran. While definitively not an expert in this area, I find pretty
obvious that changing the default integer/real type on one side and not the
other is asking for troubles. Apparently gfortran, but not the test suite, is
finding some of them as in gfortran.dg/c_loc_tests_2.f03:
[karma] f90/bug% gfc -fdefault-integer-8
/opt/gcc/gcc-4.3-work/gcc/testsuite/gfortran.dg/c_loc_tests_2.f03
/opt/gcc/gcc-4.3-work/gcc/testsuite/gfortran.dg/c_loc_tests_2.f03:53.37:
if(test_array_address(my_c_ptr_1, 100) .ne. 1) then
1
Error: Type/rank mismatch in argument 'num_elements' at (1)
/opt/gcc/gcc-4.3-work/gcc/testsuite/gfortran.dg/c_loc_tests_2.f03:83.19:
use c_loc_tests_2
1
Fatal Error: Can't open module file 'c_loc_tests_2.mod' for reading at (1): No
such file or directory
Using -fdefault-integer-8 with 'intrinsic :: iso_c_binding' should probably
trigger an error or at least a warning.
--
Summary: C/Fortran interoperability and -fdefault-integer-8
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dominiq at lps dot ens dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32957
