public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27698] subroutine _foo draws "unclassifiable statement" instead of a useful error.
Date: Sun, 05 Nov 2006 16:27:00 -0000 [thread overview]
Message-ID: <20061105162715.7221.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27698-109@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from sgk at troutmask dot apl dot washington dot edu 2006-11-05 16:27 -------
Subject: Re: subroutine _foo draws "unclassifiable statement" instead of a
useful error.
On Sun, Nov 05, 2006 at 04:19:08PM -0000, aldot at gcc dot gnu dot org wrote:
>
> ------- Comment #6 from aldot at gcc dot gnu dot org 2006-11-05 16:19 -------
> Updating the testsuite to account for the new error message now.
>
> Note that i think that we should take -fdollar-ok into account, i.e.:
>
> if (!ISALPHA (c) && !(gfc_option.flag_dollar_ok && c == '$'))
> {
> bail;
> }
>
> to allow for names (in the sense of 3.2.1) that begin with a dollar.
>
> Such names are currently rejected (even if -fdollar-ok suggests that they
> should be ok).
>
>
How does Intel's iand other commercial compilers handle
a leading dollar? The standard is quite clear that the
first character in a name is an alphabetic character.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27698
next prev parent reply other threads:[~2006-11-05 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 10:09 [Bug fortran/27698] New: " toon at moene dot indiv dot nluug dot nl
2006-05-21 11:50 ` [Bug fortran/27698] " aldot at gcc dot gnu dot org
2006-05-21 11:53 ` aldot at gcc dot gnu dot org
2006-05-21 16:14 ` kargl at gcc dot gnu dot org
2006-07-05 17:19 ` aldot at gcc dot gnu dot org
2006-07-05 17:35 ` sgk at troutmask dot apl dot washington dot edu
2006-07-05 18:55 ` patchapp at dberlin dot org
2006-11-05 16:19 ` aldot at gcc dot gnu dot org
2006-11-05 16:27 ` sgk at troutmask dot apl dot washington dot edu [this message]
2006-11-05 16:37 ` aldot at gcc dot gnu dot org
2006-11-05 17:00 ` sgk at troutmask dot apl dot washington dot edu
2006-11-05 17:16 ` aldot at gcc dot gnu dot org
2006-11-18 15:24 ` aldot at gcc dot gnu dot org
2007-01-03 16:50 ` patchapp at dberlin dot org
2007-01-07 16:24 ` aldot at gcc dot gnu dot org
2007-05-21 19:25 ` dfranke at gcc dot gnu dot org
2007-05-22 17:10 ` aldot at gcc dot gnu dot org
2007-06-10 3:07 ` jvdelisle at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061105162715.7221.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).