public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66461] [4.9/5/6 Regression] ICE on missing end program in fixed source
Date: Sat, 03 Oct 2015 00:16:00 -0000	[thread overview]
Message-ID: <bug-66461-4-Xhk0zMkoxR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66461-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #3 from kargl at gcc dot gnu.org ---
The bug surfaces at line 1439 in match.c.  The line is

  gfc_match (" if ( %e ) ", &expr);     /* Guaranteed to match.  */

The comment is wrong.  For some reason, splitting
the expression across the two lines causes a match
failure.  Changing the above to 

  m = gfc_match (" if ( %e ) ", &expr);
  if (m != MATCH_YES)
    return m;

yields

troutmask:sgk[232] gfc6 -c g5.f
g5.f:5:72:

Error: Syntax error in expression at (1)
f951: Error: Unexpected end of file in 'g5.f'

which yields a bogus error and the desired error.


  parent reply	other threads:[~2015-10-03  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 12:59 [Bug fortran/66461] New: " gerhard.steinmetz.fortran@t-online.de
2015-08-29 15:17 ` [Bug fortran/66461] [4.9/5/6 Regression] " dominiq at lps dot ens.fr
2015-10-03  0:16 ` kargl at gcc dot gnu.org [this message]
2015-10-16  8:22 ` rguenth at gcc dot gnu.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=bug-66461-4-Xhk0zMkoxR@http.gcc.gnu.org/bugzilla/ \
    --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).