public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/40330] [4.5 Regression] incorrect IO Date: Sun, 05 Jul 2009 02:12:00 -0000 [thread overview] Message-ID: <20090705021203.29724.qmail@sourceware.org> (raw) In-Reply-To: <bug-40330-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #32 from jvdelisle at gcc dot gnu dot org 2009-07-05 02:12 ------- I am getting close now. I have a patch that actually passes the CP2K test case and regression testing. It turns out that the parse_format_list function is called recursively so one must be careful about relaying information back up to the callers that a FMT_STRING token is involved and so don't save the parsed data. There is a memory leak remaining, but I know exactly what it is and what to do about it. The patch I am working on is really just a work around for the real problem. The real problem is that the pointer for literal strings in formats is clobbered by the routine that writes it. My plan is to get the above mentioned workaround patch finalized and then work toward eliminating this root problem in a subsequent patch. The final fix will involve some re-constructive surgery on the format node structure. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40330
next prev parent reply other threads:[~2009-07-05 2:12 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-03 15:45 [Bug libfortran/40330] New: [4.4 " jv244 at cam dot ac dot uk 2009-06-03 15:46 ` [Bug libfortran/40330] " jv244 at cam dot ac dot uk 2009-06-03 15:54 ` dominiq at lps dot ens dot fr 2009-06-03 16:08 ` jv244 at cam dot ac dot uk 2009-06-03 16:32 ` jv244 at cam dot ac dot uk 2009-06-03 16:47 ` jv244 at cam dot ac dot uk 2009-06-03 16:49 ` jv244 at cam dot ac dot uk 2009-06-03 16:58 ` jv244 at cam dot ac dot uk 2009-06-03 17:39 ` jb at gcc dot gnu dot org 2009-06-03 18:49 ` jb at gcc dot gnu dot org 2009-06-03 19:19 ` jb at gcc dot gnu dot org 2009-06-03 21:07 ` jb at gcc dot gnu dot org 2009-06-04 5:16 ` jv244 at cam dot ac dot uk 2009-06-04 5:37 ` burnus at gcc dot gnu dot org 2009-06-09 20:56 ` jb at gcc dot gnu dot org 2009-06-09 20:58 ` jb at gcc dot gnu dot org 2009-06-09 22:15 ` jv244 at cam dot ac dot uk 2009-06-10 2:18 ` jvdelisle at gcc dot gnu dot org 2009-06-10 3:11 ` jvdelisle at gcc dot gnu dot org 2009-06-10 6:45 ` burnus at gcc dot gnu dot org 2009-06-10 7:22 ` [Bug libfortran/40330] [4.4, 4.5 " jv244 at cam dot ac dot uk 2009-06-10 7:24 ` jv244 at cam dot ac dot uk 2009-06-10 9:26 ` jv244 at cam dot ac dot uk 2009-06-10 12:32 ` jvdelisle at gcc dot gnu dot org 2009-06-10 13:18 ` jv244 at cam dot ac dot uk 2009-06-10 21:18 ` jb at gcc dot gnu dot org 2009-06-11 1:29 ` jvdelisle at gcc dot gnu dot org 2009-06-11 2:25 ` jvdelisle at gcc dot gnu dot org 2009-06-11 7:04 ` jv244 at cam dot ac dot uk 2009-06-11 12:50 ` jvdelisle at gcc dot gnu dot org 2009-06-11 14:58 ` [Bug libfortran/40330] [4.5 " jvdelisle at gcc dot gnu dot org 2009-06-12 5:48 ` jv244 at cam dot ac dot uk 2009-06-26 15:50 ` jvdelisle at gcc dot gnu dot org 2009-07-05 2:12 ` jvdelisle at gcc dot gnu dot org [this message] 2009-07-05 12:25 ` jvdelisle at gcc dot gnu dot org 2009-07-09 1:20 ` jvdelisle at gcc dot gnu dot org 2009-07-09 1:55 ` jvdelisle at gcc dot gnu dot org 2009-07-09 1:59 ` jvdelisle at gcc dot gnu dot org 2009-07-12 14:49 ` jv244 at cam dot ac dot uk 2009-07-23 17:52 ` hjl at gcc dot gnu dot 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=20090705021203.29724.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: 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).