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: Fri, 02 Jul 2010 15:56:00 -0000 [thread overview]
Message-ID: <20100702155610.2683.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44662-16888@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from mikael at gcc dot gnu dot org 2010-07-02 15:56 -------
(In reply to comment #5)
> If you need someone to apply, test and commit , let me know. I will have time
> and its pretty quick on my quad machine
>
No thanks, I will need a commit tree anyway.
It's currently bootstrapping so it's a matter of hours now.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44662
next prev parent reply other threads:[~2010-07-02 15:56 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
2010-07-01 19:10 ` jvdelisle at gcc dot gnu dot org
2010-07-02 15:56 ` mikael at gcc dot gnu dot org [this message]
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=20100702155610.2683.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).