public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerhard.steinmetz.fortran@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66039] New: ICE on incomplete parentheses at rewind, flush, endfile, backspace
Date: Wed, 06 May 2015 17:15:00 -0000	[thread overview]
Message-ID: <bug-66039-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 66039
           Summary: ICE on incomplete parentheses at rewind, flush,
                    endfile, backspace
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gerhard.steinmetz.fortran@t-online.de
  Target Milestone: ---

Created attachment 35483
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35483&action=edit
more code variants

An ICE occurs with incomplete parentheses at rewind, flush, endfile, backspace.
For example :

   program p
      flush ((
   end

Tested with gfortran -c, versions 4.8.3, 4.9.0, 5.1.1
on SUSE Linux 13.2 (64 bit)

The attachement contains more disrupting variants for rewind, flush, endfile,
backspace.
Interestingly, for that variants there are no ICEs for the statement wait.

Kind regards.


             reply	other threads:[~2015-05-06 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:15 gerhard.steinmetz.fortran@t-online.de [this message]
2015-05-06 19:59 ` [Bug fortran/66039] " kargl at gcc dot gnu.org
2015-05-18 21:05 ` kargl at gcc dot gnu.org
2015-05-19 17:13 ` kargl at gcc dot gnu.org
2015-05-19 17:14 ` kargl 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-66039-4@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).