This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/33445] Diagnose "!$OMP&" as an error in free format unless it is a continuation line
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Sep 2007 13:46:33 -0000
- Subject: [Bug fortran/33445] Diagnose "!$OMP&" as an error in free format unless it is a continuation line
- References: <bug-33445-15101@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from burnus at gcc dot gnu dot org 2007-09-19 13:46 -------
(In reply to comment #6)
> > Pedantically this is not a bug. If an omp sentinel doesn't have the desired
> > form, it should be handled as a normal comment.
I cannot find anything about this in the OpenMP spec; I think the behaviour of
the compiler is undefined as this is invalid syntax. I don't find anything
which indicates that this has to/should/would be treated as comment.
(In reply to comment #7)
> Only a warning, please. Not an error for code that is, strictly speaking,
> valid.
I am actually in favour of an error unless someone can points out the part of
the spec which implies this is valid or a pice of code which shows that it
would be sensible to accept "!OMP$&" + garbage as comment.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33445