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 fortran/59700] [4.8/4.9 Regression] Misleading/buggy runtime error message: Bad integer for item 0 in list input
Date: Fri, 10 Jan 2014 22:29:00 -0000	[thread overview]
Message-ID: <bug-59700-4-BZvG2cq8Xa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59700-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I agree with Jerry that the errors with logical can be fixed later (AFAICT they
are not a regression up to 4.3.1).

I also think the error

   read(fd, *, err=31, iomsg=msg) i1, x2, a, x1
31 if (msg /= 'Bad repeat count in item 3 of list input') call abort

is bogus (IIRC repeat count needs a '*').


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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 14:45 [Bug fortran/59700] New: " mvondomaros at gmail dot com
2014-01-06 23:24 ` [Bug fortran/59700] [4.8/4.9 Regression] " kargl at gcc dot gnu.org
2014-01-07 11:54 ` rguenth at gcc dot gnu.org
2014-01-09  9:27 ` dominiq at lps dot ens.fr
2014-01-09 15:39 ` sgk at troutmask dot apl.washington.edu
2014-01-09 15:44 ` sgk at troutmask dot apl.washington.edu
2014-01-09 20:41 ` dominiq at lps dot ens.fr
2014-01-09 20:58 ` dominiq at lps dot ens.fr
2014-01-09 21:09 ` sgk at troutmask dot apl.washington.edu
2014-01-09 21:27 ` dominiq at lps dot ens.fr
2014-01-09 21:39 ` sgk at troutmask dot apl.washington.edu
2014-01-09 22:48 ` dominiq at lps dot ens.fr
2014-01-10  4:18 ` jvdelisle at gcc dot gnu.org
2014-01-10 17:09 ` jvdelisle at gcc dot gnu.org
2014-01-10 22:29 ` dominiq at lps dot ens.fr [this message]
2014-01-10 22:39 ` jvdelisle at gcc dot gnu.org
2014-01-10 23:11 ` sgk at troutmask dot apl.washington.edu
2014-01-11  0:55 ` dominiq at lps dot ens.fr
2014-01-11 18:57 ` jvdelisle at gcc dot gnu.org
2014-01-11 21:39 ` jvdelisle at gcc dot gnu.org
2014-02-22  0:02 ` jvdelisle at gcc dot gnu.org
2014-02-22  0:34 ` sgk at troutmask dot apl.washington.edu
2014-02-22  2:12 ` jvdelisle at gcc dot gnu.org
2014-02-22  2:51 ` jvdelisle at gcc dot gnu.org
2014-02-22  2:53 ` 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-59700-4-BZvG2cq8Xa@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).