[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-08-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2010-08-02 13:19 --- Closing as fixed. Regarding comment #7. I do not see the problem on 4.5. I reran tests here on my machine that failed with 4.6 and there were no failures on 4.5 -- jvdelisle at gcc dot gnu dot org changed:

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-08-01 Thread burnus at gcc dot gnu dot org
--- Comment #13 from burnus at gcc dot gnu dot org 2010-08-01 19:38 --- (In reply to comment #12) > This appears to be fixed now from the commit of patch in #10. Which is the commit: Date: Sat Jul 31 21:37:25 2010 New Revision: 162788 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-08-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2010-08-01 17:28 --- This appears to be fixed now from the commit of patch in #10. The related failures showing in gcc test results are no longer there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45131

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2010-07-31 17:04 --- I see the problem with 4.4.3 as well. I think the patch in #10 is only masking it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45131

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2010-07-31 16:28 --- I can see one here on a 32 bit machine. Moving string.h down in the file as noted by David Edelsohn fixes it. I also changed the return type to void in trans-io.c. Index: inquire.c =

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-30 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2010-07-30 15:11 --- I can also reproduce it with -m32 and x86-64. The dump looks OK; if one uses a debugger, one sees that in inquire_via_unit: u->last_record == 0 - instead of the expect "5". but u->flags.access == ACCESS_DIRECT as e

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2010-07-30 14:06 --- #7 confirms my suspicions. I will try to have a look into this in the next few days. If anyone else has time, please do. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45131

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-30 Thread rguenth at gcc dot gnu dot org
--- Comment #7 from rguenth at gcc dot gnu dot org 2010-07-30 09:32 --- I see the same with -m32 on x86_64. Interestingly I see it with -O0 and libgfortran from 4.5 as well, so it looks like a frontend problem, not a library problem to me. -- rguenth at gcc dot gnu dot org changed:

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-07-30 01:49 --- This is really odd because the patch does not touch these parts of the library, at least for inquire_3.f90. I wonder if there is something latent here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45131

[Bug fortran/45131] [4.6 regression] New Fortran test failures

2010-07-29 Thread hjl dot tools at gmail dot com
--- Comment #5 from hjl dot tools at gmail dot com 2010-07-29 15:47 --- (In reply to comment #4) > HJ, as it works on most systems, can you do some debugging? Trunk was broken since yesterday and was fixed a while ago. > a) Does the system has HAVE_TTYNAME defined for libgfortran/ ? Y