public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44662] unitialized memory on testcases abstract_type_6.f03 and typebound_call_4.f03 Date: Thu, 01 Jul 2010 17:05:00 -0000 [thread overview] Message-ID: <20100701170525.21210.qmail@sourceware.org> (raw) In-Reply-To: <bug-44662-16888@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from mikael at gcc dot gnu dot org 2010-07-01 17:05 ------- PR44746 is a probable duplicate. I should hurry to commit before some others show up. I need to * finish what I'm doing * retrieve my commit key from... well, where it is * find some space to save my work * actually save it * exercise my memory on that f*** pass phrase * checkout a fresh tree * bootstrap * test again, just to be sure * finally commit I will report if I'm still stuck at step 2 next week, so that, would someone have extra time, he could loose it in fixing this PR. -- mikael at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |mikael at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-07-01 17:05:25 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44662
next prev parent reply other threads:[~2010-07-01 17:05 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-25 9:16 [Bug fortran/44662] New: " mikael at gcc dot gnu dot org 2010-06-25 9:45 ` [Bug fortran/44662] " mikael at gcc dot gnu dot org 2010-06-25 11:29 ` mikael at gcc dot gnu dot org 2010-06-28 8:48 ` dominiq at lps dot ens dot fr 2010-07-01 17:05 ` mikael at gcc dot gnu dot org [this message] 2010-07-01 19:10 ` jvdelisle at gcc dot gnu dot org 2010-07-02 15:56 ` mikael at gcc dot gnu dot org 2010-07-02 20:01 ` mikael at gcc dot gnu dot org 2010-07-03 10:41 ` mikael 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=20100701170525.21210.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).