This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/30617] recursive I/O hangs under OSX
- From: "dominiq at lps dot ens dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Feb 2007 10:03:29 -0000
- Subject: [Bug libfortran/30617] recursive I/O hangs under OSX
- References: <bug-30617-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #18 from dominiq at lps dot ens dot fr 2007-02-08 10:03 -------
Subject: Re: recursive I/O hangs under OSX
> gfortran.dg/intrinsic_actual_2.f90 fails on Linux too when linked with
> -fopenmp (or -lpthread, -fopenmp implies that), but that is fine, the testcase
> is IMHO not valid Fortran95 source.
When you say "fails" what kind of failure do you get? Is this a timeout or not?
If this is a runtime error, a "seg fault", or whatever but hanging, this is
fine
with me.
> Now, if Fortran2003 allows some recursive access to the same unit (under which
> conditions?)
I think the question is settled: recursive access to external units is invalid.
> then anyone calling gfc_unit could then check the recursion count and if it is bigger than 1,
> unlock_unit it again and report an error.
This seems the path to follow to implement a runtime error, isn't it?
To be frank, I have a very limited understanding of what you are saying, but
I could look again to the code to figure out what it looks like: I understand
more or less the technical concepts, but not the actual implementation.
Thanks for your time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617