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, 27 Mar 2013 20:24:00 -0000 [thread overview] Message-ID: <bug-56737-4-z0IEcUHDLe@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 #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-27 20:24:11 UTC --- If one sets the breakpoint in _gfortrani_next_format, one gets for the original, non cached version: (gdb) p dtp->u.p.fmt.array.array[1].source $13 = 0x7fffffffdec6 "1H ),6h===== ,a 12,i4,6h =====)", ... For the second round, one gets: (gdb) p dtp->u.p.fmt.array.array[1].source $14 = 0x7fffffffdec6 ' ' <repeats 26 times>, "=====) \f" Thus, the "source" string is not carried over.
next prev parent reply other threads:[~2013-03-27 20:24 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 [this message] 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 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-z0IEcUHDLe@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: linkBe 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).