public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/56737] [4.6/4.7/4.8/4.9 Regression] Wrong I/O result with format cache for Hollerith strings
Date: Wed, 03 Apr 2013 14:07:00 -0000	[thread overview]
Message-ID: <bug-56737-4-26TdUvgG4t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56737-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-04-03 14:07:02 UTC ---
(In reply to comment #8)
> 2013-04-03  Tobias Burnus  <burnus@net-b.de>
> 
>         Backport from mainline:
>         2013-03-29  Tobias Burnus  <burnus@net-b.de>
> 
>         PR fortran/56737
>         * io/format.c (parse_format): With caching, copy
>         dtp->format string.
>         (save_parsed_format): Use dtp->format directly without
>         copying.

I forgot to include the following bits in the commit log - it's in the
ChangeLog and in the commit:

>        2012-03-29  Tobias Burnus  <burnus@net-b.de>
>
>        PR fortran/56737
>        * io/format.c (parse_format_list): Also cache FMT_STRING.
>        (parse_format): Update call.



So far, the issue is fixed on the trunk and the 4.7 and 4.8 branches; GCC 4.7.3
is scheduled to be released in the next days.  (Backporting to 4.6 is still
pending.)


  parent reply	other threads:[~2013-04-03 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 11:46 [Bug libfortran/56737] New: Bizarre Hollerith edit descriptor errors (valgrind shows uninitialized value in libgfortran) jonathan.hogg at stfc dot ac.uk
2013-03-27 19:32 ` [Bug libfortran/56737] [4.6/4.7/4.8/4.9 Regression] Wrong I/O result with format cache for Hollerith strings burnus at gcc dot gnu.org
2013-03-27 20:24 ` burnus at gcc dot gnu.org
2013-03-28 10:00 ` burnus at gcc dot gnu.org
2013-03-29  9:38 ` burnus at gcc dot gnu.org
2013-03-29  9:40 ` burnus at gcc dot gnu.org
2013-04-02 15:43 ` burnus at gcc dot gnu.org
2013-04-03 10:15 ` rguenth at gcc dot gnu.org
2013-04-03 14:02 ` burnus at gcc dot gnu.org
2013-04-03 14:07 ` burnus at gcc dot gnu.org [this message]
2013-04-04  9:32 ` burnus at gcc dot gnu.org
2013-04-04  9:38 ` burnus at gcc dot gnu.org
2013-04-04 10:43 ` jonathan.hogg at stfc dot ac.uk

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-56737-4-26TdUvgG4t@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).