public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35864] [4.4 Regression] Revision 133965 broke gfortran.dg/initialization_1.f90 Date: Tue, 15 Apr 2008 19:44:00 -0000 [thread overview] Message-ID: <20080415194336.23460.qmail@sourceware.org> (raw) In-Reply-To: <bug-35864-507@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from pault at gcc dot gnu dot org 2008-04-15 19:43 ------- Finally, I have managed to deal with this. Sorry it took so long Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35864
next prev parent reply other threads:[~2008-04-15 19:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-07 23:19 [Bug fortran/35864] New: [4.4 Regression] Revision 133965 broke gfortran.dg/initialization_1.f90 for cris-elf hp at gcc dot gnu dot org 2008-04-07 23:49 ` [Bug fortran/35864] " jvdelisle at verizon dot net 2008-04-08 0:13 ` hp at gcc dot gnu dot org 2008-04-08 15:16 ` [Bug fortran/35864] [4.4 Regression] Revision 133965 broke gfortran.dg/initialization_1.f90 dominiq at lps dot ens dot fr 2008-04-08 20:06 ` jvdelisle at gcc dot gnu dot org 2008-04-09 11:46 ` burnus at gcc dot gnu dot org 2008-04-09 23:48 ` jvdelisle at gcc dot gnu dot org 2008-04-09 23:58 ` hp at gcc dot gnu dot org 2008-04-10 0:00 ` hp at gcc dot gnu dot org 2008-04-11 9:55 ` pault at gcc dot gnu dot org 2008-04-11 12:24 ` burnus at gcc dot gnu dot org 2008-04-15 19:42 ` pault at gcc dot gnu dot org 2008-04-15 19:44 ` pault at gcc dot gnu dot org [this message] 2008-05-01 7:33 ` pault 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=20080415194336.23460.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).