[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-25 Thread ghazi at gcc dot gnu dot org
--- Comment #7 from ghazi at gcc dot gnu dot org 2007-04-25 18:07 --- Patch installed -- ghazi at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-25 Thread ghazi at gcc dot gnu dot org
--- Comment #8 from ghazi at gcc dot gnu dot org 2007-04-25 18:08 --- Updated testsuite results: http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg01287.html -- ghazi at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-23 Thread ghazi at gcc dot gnu dot org
--- Comment #6 from ghazi at gcc dot gnu dot org 2007-04-23 08:52 --- Subject: Bug 31616 Author: ghazi Date: Mon Apr 23 08:52:24 2007 New Revision: 124059 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=124059 Log: PR fortran/31616 * gfortran.dg/open_errors.f90:

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-22 Thread ghazi at gcc dot gnu dot org
--- Comment #5 from ghazi at gcc dot gnu dot org 2007-04-23 05:58 --- Patch posted here: http://gcc.gnu.org/ml/gcc-patches/2007-04/msg01457.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31616

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-18 Thread ghazi at gcc dot gnu dot org
--- Comment #2 from ghazi at gcc dot gnu dot org 2007-04-18 06:58 --- (In reply to comment #1) Try changing: call abort() to: print *, msg This will then print the error messages instead of aborting and you may be able to see what is going on. If I make your suggested change,

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2007-04-19 04:05 --- It looks like this platform has different error messages for a given error. I suggest that this test case be either marked as expected to fail for this platform or we could delete the test case altogether.

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-18 Thread ghazi at gcc dot gnu dot org
--- Comment #4 from ghazi at gcc dot gnu dot org 2007-04-19 04:49 --- (In reply to comment #3) It looks like this platform has different error messages for a given error. Yes that's correct. I ran open_errors.exe under the solaris truss command and saw this: open64(./,

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-04-18 05:48 --- This could be as simple as the error messages returned by the OS don't match what we put in the test case. Try changing: call abort() to: print *, msg This will then print the error messages instead of

[Bug fortran/31616] testsuite failures in gfortran.dg/open_errors.f90

2007-04-17 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last