gcc 4.1 FAIL: gfortran.dg/large_integer_kind_1.f90 on sparc/sparc64 linux...

[Christian Joensson]

Sorry, this may be more appropriate I guess...

---------- Forwarded message ----------
From: Christian Joensson <christian.joensson@gmail.com>
Date: Oct 4, 2005 11:20 AM
Subject: gcc 4.1 FAIL: gfortran.dg/large_integer_kind_1.f90 on
sparc/sparc64 linux...
To: gcc mailing list <gcc@gcc.gnu.org>


In http://gcc.gnu.org/ml/gcc-testresults/2005-10/msg00130.html, and a
few previous postings of testsuite results on sparc/sparc64 linux, I
get this gfortran failure:


Executing on host:
/usr/local/src/trunk/objdir/gcc/testsuite/../gfortran
-B/usr/local/src/trunk/objdir/gcc/testsuite/../
/usr/local/src/trunk/gcc/gcc/testsuite/gfortran.dg/large_integer_kind_1.f90
  -O0   -pedantic-errors
-L/usr/local/src/trunk/objdir/sparc64-unknown-linux-gnu/./libgfortran/.libs
-L/usr/local/src/trunk/objdir/sparc64-unknown-linux-gnu/./libiberty
-lm   -o ./large_integer_kind_1.exe    (timeout = 1200)
  In file /usr/local/src/trunk/gcc/gcc/testsuite/gfortran.dg/large_integer_kind_1.f90:8

    integer(kind=k),intent(in) :: a
                 1
Error: Kind -1 not supported for type INTEGER at (1)
  In file /usr/local/src/trunk/gcc/gcc/testsuite/gfortran.dg/large_integer_kind_1.f90:25

  use testmod
            1
Fatal Error: Can't open module file 'testmod.mod' for reading at (1):
No such file or directory
compiler exited with status 1
output is:
  In file /usr/local/src/trunk/gcc/gcc/testsuite/gfortran.dg/large_integer_kind_1.f90:8

    integer(kind=k),intent(in) :: a
                 1
Error: Kind -1 not supported for type INTEGER at (1)
  In file /usr/local/src/trunk/gcc/gcc/testsuite/gfortran.dg/large_integer_kind_1.f90:25

  use testmod
            1
Fatal Error: Can't open module file 'testmod.mod' for reading at (1):
No such file or directory

FAIL: gfortran.dg/large_integer_kind_1.f90  -O0  (test for excess errors)

There are, also, more of the same type of error.

Now, is this what I should expect?

Is it perhaps even addressed by the recently commited patch to libgfortran?

If none of the above, may a kernel/glibc/binutils problem lurk here?

Would you like me to file this with bugzilla?

--
Cheers,

/ChJ


--
Cheers,

/ChJ