This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/27698] subroutine _foo draws "unclassifiable statement" instead of a useful error.
- From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jul 2006 17:35:38 -0000
- Subject: [Bug fortran/27698] subroutine _foo draws "unclassifiable statement" instead of a useful error.
- References: <bug-27698-109@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from sgk at troutmask dot apl dot washington dot edu 2006-07-05 17:35 -------
Subject: Re: subroutine _foo draws "unclassifiable statement" instead of a
useful error.
On Wed, Jul 05, 2006 at 05:19:44PM -0000, aldot at gcc dot gnu dot org wrote:
>
>
> ------- Comment #3 from aldot at gcc dot gnu dot org 2006-07-05 17:19 -------
> (In reply to comment #2)
> > Bernhard,
> >
> > Your patch only addresses one aspect of the problem.
> > Consider
> >
> > function _foo
> > entry _bar
> > end function
> >
>
> Is it sufficient to print an error in gfc_match_name, or should the individual
> callers be instrumented with separate messages (invalid form for
> $everything_with_a_name at $there) ?
>
I think we can issue the error in gfc_match_name with some
generic message such as
gcc_error("Object at %L cannot have a leading underscore", locus);
I had forgotten about this PR. Thanks for following up.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27698