This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/35840] ICE for character expression in I/O specifier
- From: "mikael dot morin at tele2 dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Sep 2008 19:42:20 -0000
- Subject: [Bug fortran/35840] ICE for character expression in I/O specifier
- References: <bug-35840-13404@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #14 from mikael dot morin at tele2 dot fr 2008-09-15 19:42 -------
Sorry Jerry, I didn't read your message (I mean the one to the list with the
patch to io.c) before.
I have just checked again, the patch does work for me.
And Dominique agrees with me. :)
(In reply to comment #11)
> We should review all such tags against the standard to make sure we don't
> miss any others.
I have just done it. Asynchronous in data transfer statements is the only case
requiring an initialization expression.
> It seems odd to me that only asynchronous= has this requirement.
>
to me too.
Note 9.29:
[...]
The ASYNCHRONOUS= specifier value in a data transfer statement is an
initialization expression because it effects compiler optimizations and,
therefore, needs to be known at compile time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35840