public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/59764] Read logicals, line buffer, item_count, and error message consistancy
Date: Fri, 10 Jan 2014 22:26:00 -0000	[thread overview]
Message-ID: <bug-59764-4-gA7dxv019W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59764-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59764

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-10
     Ever confirmed|0                           |1
      Known to fail|                            |4.7.3, 4.8.2, 4.9.0

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed. The test in pr59700 comment 6 when compiled with gfortran 4.3.1
returns

 Bad logical value while reading item 0                                         

(replacing the 'call abort' with 'print *, msg').


  parent reply	other threads:[~2014-01-10 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-59764-4@http.gcc.gnu.org/bugzilla/>
2014-01-10 19:20 ` jvdelisle at gcc dot gnu.org
2014-01-10 22:26 ` dominiq at lps dot ens.fr [this message]
2014-01-10 22:31 ` jvdelisle at gcc dot gnu.org
2014-01-11 18:57 ` jvdelisle at gcc dot gnu.org
2014-02-21 23:57 ` jvdelisle at gcc dot gnu.org
2014-02-22  2:12 ` jvdelisle 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-59764-4-gA7dxv019W@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).