[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #16 from pinskia at gcc dot gnu dot org 2006-02-19 02:57 --- (In reply to comment #15) > processor-dependent in Fortan means compiler dependent In the same way implemenation defined code is in C and C++. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #15 from pinskia at gcc dot gnu dot org 2006-02-19 02:56 --- >From Fortran 2003 9.1.2: An unformatted record consists of a sequence of values in a processor-dependent form and may contain data of any type or may contain no data. processor-dependent in Fortan means compiler

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #14 from pinskia at gcc dot gnu dot org 2006-02-19 02:46 --- Read: http://gcc.gnu.org/ml/fortran/2004-12/msg00139.html Basicially unformatted input was never meant to be portable. The way for them to fix their issue is to have a program that writes out the unformatted data

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread hjl at lucon dot org
--- Comment #12 from hjl at lucon dot org 2006-02-19 02:43 --- Please provide more details on this issue since this is a gcc only problem. I need references to Fortran standard when I talk to our SPEC people. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread hjl at lucon dot org
--- Comment #13 from hjl at lucon dot org 2006-02-19 02:44 --- Need more info. -- hjl at lucon dot org changed: What|Removed |Added Status|RESOLVED

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-02-19 02:31 --- This is invalid really as the problem is different size of record header. There is a bug to fix this (PR 19303) but really this is just unportantable data even with the little/big endian issue fixed. Please report

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread hjl at lucon dot org
--- Comment #10 from hjl at lucon dot org 2006-02-19 02:25 --- FYI, there are only 2 different input files for this benchmark, little endian and big endian. My testcase should be valid for all little endian machines. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread hjl at lucon dot org
--- Comment #9 from hjl at lucon dot org 2006-02-19 02:23 --- I didn't check how the data was generated. It is taken from a Linux/i686 machine. I doubt it is invalid. At least, it should be valid on Linux/i686. Another Fortran compiler has no problem with the testcase. Jerry, does my O

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-02-19 01:59 --- #6 works on i686 as well. If SPEC 2006 is indeed using non-portable data then we need to notify. HJ can you look into this for us? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-02-19 01:41 --- (In reply to comment #5) > This points to a compatibility issue, but the fact that it did not fail on the > first read and did on the second is suspicious. Not really as there was enough data for the first one but n

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-02-19 01:40 --- This program works on powerpc-darwin (and most likely other targets too): program pr INTEGER, PARAMETER :: MG=16 REAL,SAVE :: abscoefL1(5,13,MG),abscoefH1(5,13:59,MG), & SELFREF1(10

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-02-19 01:40 --- I get: ./a.out At line 15 of file foo.f90 Fortran runtime error: Corrupt unformatted sequential file This points to a compatibility issue, but the fact that it did not fail on the first read and did on the secon

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-02-19 01:30 --- http://gcc.gnu.org/onlinedocs/gcc-3.0.1/g77_20.html#SEC662 Says they are not portable. Why are they trying to use unformatted input? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-02-19 01:20 --- I am tempting at closing this as invalid. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-02-19 01:19 --- unformated input is not portable at all and should be baned from SPEC unless the test is also writting out the unformated data. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26357

[Bug libfortran/26357] Unformated input doesn't work

2006-02-18 Thread hjl at lucon dot org
--- Comment #1 from hjl at lucon dot org 2006-02-19 01:15 --- Created an attachment (id=10876) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10876&action=view) A testcase I got [EMAIL PROTECTED] unformated]$ make /export/build/gnu/gcc/build-x86_64-linux/gcc/gfortran -B/export/bui