------- Comment #6 from kargl at gcc dot gnu dot org 2007-02-11 22:26 -------
daniel,
It's just an inconsistency in implementations. First, note that
FX and myself implemented a lot of the g77 intrinsics procedures
as our first foray into gfortran, so we may have missed some of the
finer details. For example, EXIT() actually accepts any integer
kind. I don't know if it's documented or not. I'll note
laptop:kargl[210] cat > e.f90
program e
integer(1) i1
integer(2) i2
integer(4) i4
integer(8) i8
call exit(i1)
call exit(i2)
call exit(i3)
call exit(i8)
end program e
laptop:kargl[211] gfc4x -o z -fdump-tree-original e.f90
/usr/tmp/ccA5UbZ9.o(.text+0x1e): In function `MAIN__':
: undefined reference to `_gfortran_exit_i1'
collect2: ld returned 1 exit status
laptop:kargl[212] more e.f90.003t.original
MAIN__ ()
{
int2 i2;
int1 i1;
int8 i8;
int4 i3;
_gfortran_set_std (70, 127, 0, 0);
_gfortran_exit_i1 (&i1);
_gfortran_exit_i2 (&i2);
_gfortran_exit_i4 (&i3);
_gfortran_exit_i8 (&i8);
}
So, I think we need to audit the intrinsics to see were we need to
fix up the inconsistencies and documentation.
--
kargl at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372
