public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15502] [meta-bug] bugs needed for SPEC CPU 2K and 2K5/6 and 95 Date: Wed, 02 Nov 2005 21:13:00 -0000 [thread overview] Message-ID: <20051102211337.18417.qmail@sourceware.org> (raw) In-Reply-To: <bug-15502-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-02 21:13 ------- Note there are still some more 2k5/6 SPEC blocking bugs which just had not been filed yet. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15502
next parent reply other threads:[~2005-11-02 21:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15502-6528@http.gcc.gnu.org/bugzilla/> 2005-11-02 21:13 ` pinskia at gcc dot gnu dot org [this message] 2005-11-05 21:53 ` tkoenig at gcc dot gnu dot org 2006-01-01 5:48 ` pinskia at gcc dot gnu dot org 2006-01-10 0:12 ` tobi at gcc dot gnu dot org 2006-01-23 18:15 ` pinskia at gcc dot gnu dot org 2006-01-23 18:21 ` pinskia at gcc dot gnu dot org 2006-06-01 19:19 ` [Bug fortran/15502] [meta-bug] bugs needed for SPEC CPU 2K and 2K6 " pault at gcc dot gnu dot org 2004-05-18 13:06 [Bug fortran/15502] New: [meta-bug] bugs needed for SPEC CPU 2K and 2K4 pinskia at gcc dot gnu dot org 2005-08-02 10:24 ` [Bug fortran/15502] [meta-bug] bugs needed for SPEC CPU 2K and 2K5/6 and 95 steven at gcc dot gnu dot org 2005-09-09 6:02 ` rsandifo at gcc dot gnu dot org 2005-09-09 22:17 ` pinskia at gcc dot gnu dot org 2005-09-13 2:12 ` pinskia at gcc dot gnu dot org 2005-09-14 15:42 ` pinskia at gcc dot gnu dot org 2005-09-16 16:30 ` steven at gcc dot gnu dot org 2005-09-16 16:43 ` pinskia at gcc dot gnu dot org 2005-09-18 20:03 ` tkoenig 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=20051102211337.18417.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).