public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32834] [Meta-bug] 'Fortran 95'-only failures
Date: Fri, 20 Jul 2007 17:03:00 -0000 [thread overview]
Message-ID: <20070720170251.19206.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32834-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from jv244 at cam dot ac dot uk 2007-07-20 17:02 -------
(In reply to comment #2)
> Should we open another PR for wrong-code errors?
no, I overlooked that keyword, and they belong to this category (though I'll
again ignore arch specific ones). I'll add them to the list shortly.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32834
next prev parent reply other threads:[~2007-07-20 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 8:13 [Bug fortran/32834] New: [Meta-bugs] " jv244 at cam dot ac dot uk
2007-07-20 8:20 ` [Bug fortran/32834] " jv244 at cam dot ac dot uk
2007-07-20 12:25 ` [Bug fortran/32834] [Meta-bug] " burnus at gcc dot gnu dot org
2007-07-20 16:42 ` tkoenig at gcc dot gnu dot org
2007-07-20 17:03 ` jv244 at cam dot ac dot uk [this message]
2007-07-20 17:17 ` jv244 at cam dot ac dot uk
[not found] <bug-32834-4@http.gcc.gnu.org/bugzilla/>
2015-01-24 15:22 ` tkoenig at gcc dot gnu.org
2015-01-24 21:32 ` tkoenig at gcc dot gnu.org
2015-05-04 14:31 ` fxcoudert at gcc dot gnu.org
2015-06-04 18:58 ` tkoenig at gcc dot gnu.org
2015-06-05 20:42 ` kargl at gcc dot gnu.org
2020-05-28 9:50 ` markeggleston at gcc dot gnu.org
2022-05-16 20:38 ` anlauf at gcc dot gnu.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=20070720170251.19206.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).