public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43155] I/O error message: Off-by one position of edit descriptor
Date: Sat, 27 Feb 2010 19:26:00 -0000	[thread overview]
Message-ID: <20100227192625.17747.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43155-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from burnus at gcc dot gnu dot org  2010-02-27 19:26 -------
I think the main problem of comment 0 was a user error - or at least it is not
reproducible with the information we have.

The second problem is solved. I therefore changed the summary and close it as
FIXED.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
            Summary|Reading real numbers of the |I/O error message: Off-by
                   |form "123+ 44" (with space) |one position of edit
                   |                            |descriptor


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


      parent reply	other threads:[~2010-02-27 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 20:58 [Bug fortran/43155] New: Reading real numbers of the form "123+ 44" (with space) burnus at gcc dot gnu dot org
2010-02-23 21:28 ` [Bug fortran/43155] " kargl at gcc dot gnu dot org
2010-02-24  2:55 ` jvdelisle at gcc dot gnu dot org
2010-02-24  4:01 ` jvdelisle at gcc dot gnu dot org
2010-02-24  7:06 ` burnus at gcc dot gnu dot org
2010-02-25  5:52 ` jvdelisle at gcc dot gnu dot org
2010-02-27 19:26 ` burnus at gcc dot gnu dot org [this message]

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=20100227192625.17747.qmail@sourceware.org \
    --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).