public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi 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 and 95 Date: Mon, 20 Sep 2004 09:39:00 -0000 [thread overview] Message-ID: <20040920093909.30456.qmail@sourceware.org> (raw) In-Reply-To: <20040517200031.15502.pinskia@gcc.gnu.org> -- Bug 15502 depends on bug 15364, which changed state. Bug 15364 Summary: Array fields in derived types not printed correctly. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15364 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15502
next prev parent reply other threads:[~2004-09-20 9:39 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 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 2004-05-18 13:38 ` [Bug fortran/15502] " pinskia at gcc dot gnu dot org 2004-05-24 1:24 ` pbrook at gcc dot gnu dot org 2004-05-26 22:57 ` pinskia at gcc dot gnu dot org 2004-06-01 2:25 ` pinskia at gcc dot gnu dot org 2004-06-09 13:09 ` tobi at gcc dot gnu dot org 2004-08-09 23:33 ` pbrook at gcc dot gnu dot org 2004-08-10 1:05 ` pinskia at gcc dot gnu dot org 2004-08-18 2:22 ` pinskia at gcc dot gnu dot org 2004-08-21 15:28 ` pinskia at gcc dot gnu dot org 2004-08-23 0:08 ` rth at gcc dot gnu dot org 2004-08-25 16:52 ` pbrook at gcc dot gnu dot org 2004-09-20 9:39 ` tobi at gcc dot gnu dot org [this message] 2004-09-20 13:02 ` [Bug fortran/15502] [meta-bug] bugs needed for SPEC CPU 2K and 2K5 and 95 pinskia at gcc dot gnu dot org 2004-10-06 19:00 ` pbrook at gcc dot gnu dot org 2004-11-11 14:34 ` pbrook at gcc dot gnu dot org 2005-01-11 0:18 ` steven at gcc dot gnu dot org 2005-01-17 16:01 ` pinskia at gcc dot gnu dot org 2005-03-01 0:44 ` tobi at gcc dot gnu dot org 2005-04-30 17:53 ` pinskia at gcc dot gnu dot org 2005-06-05 22:47 ` pault at gcc dot gnu dot org 2005-06-05 22:49 ` pault at gcc dot gnu dot org 2005-06-06 0:11 ` pinskia at gcc dot gnu dot org 2005-07-16 20:47 ` 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 " 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=20040920093909.30456.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).