[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-12 Thread howarth at nitro dot med dot uc dot edu
--- Comment #11 from howarth at nitro dot med dot uc dot edu 2009-01-13 00:52 --- Created an attachment (id=17081) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17081action=view) test program demonstrating missing error condition --

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-12 Thread howarth at nitro dot med dot uc dot edu
--- Comment #12 from howarth at nitro dot med dot uc dot edu 2009-01-13 00:55 --- The attached badread,f test program produces... F ...when attempting to read a float with... READ(TEMP,'(F20.0)',ERR=) R from TEMP='END' when run against the

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-01-11 16:43 --- Reviewing code carefully, I found the following. I can not confirm this is the problem, but removing this portion of code does not cause a regression in our current testsuite. This snippit was left over from

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-11 Thread howarth at nitro dot med dot uc dot edu
--- Comment #10 from howarth at nitro dot med dot uc dot edu 2009-01-11 23:00 --- The patch in comment 9 doesn't solve the issue with xplor-nih. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38772

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-10 Thread howarth at nitro dot med dot uc dot edu
--- Comment #8 from howarth at nitro dot med dot uc dot edu 2009-01-10 19:57 --- Jerry, If I use the following patch to xplor-nih --- xrmani.f.org2009-01-09 17:48:46.0 -0500 +++ xrmani.f2009-01-10 14:29:42.0 -0500 @@ -363,6 +363,7 @@ END IF

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-09 Thread howarth at nitro dot med dot uc dot edu
--- Comment #6 from howarth at nitro dot med dot uc dot edu 2009-01-09 16:28 --- Jerry, Your test program doesn't produce an error under ifort 10.1.015. I'll try to pinpoint the exact failure this weekend. At the moment, the problem appears to be in the code that reads the

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-09 Thread howarth at nitro dot med dot uc dot edu
--- Comment #7 from howarth at nitro dot med dot uc dot edu 2009-01-10 00:10 --- Jerry, It appears that the numerical values for all of the refinement table entries are properly read. However for some reason the next line with the 'end' statement gets lost. I have to duplicate this

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-08 Thread kargl at gcc dot gnu dot org
--- Comment #1 from kargl at gcc dot gnu dot org 2009-01-09 01:47 --- Without a testcase, it is difficult to determine if the problem is with gfortran or a bug in your application. From Section 9.2.2.1, Internal File Properties, (8) On input, blanks are treated in the same way as

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-08 Thread howarth at nitro dot med dot uc dot edu
--- Comment #2 from howarth at nitro dot med dot uc dot edu 2009-01-09 02:14 --- I've contacted the author of xplor-nih as the parsing code is pretty complex legacy fortran. However I would note that they build this code with the a variety of commercial fortran compilers. PowerPC

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-01-09 03:00 --- I am looking into it. Thanks for the report. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38772

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-01-09 03:32 --- I have reviewed our library code to see if we are handling BLANK=status correctly. AFAICT we are doing this right. I was concerned with your report because I thought maybe we were getting a side effect from the

[Bug libfortran/38772] r143102 breaks xplor-nih

2009-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-01-09 04:03 --- g77, ifort, and gfortran 4.4 all pass this test case which should print nothing. c { dg-do run } c PR38097 I/O with blanks in exponent fails; BN edit descriptor c Test case derived from reporter.