public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: dalej@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/7133: PPC: unrecognizable insn
Date: Tue, 22 Oct 2002 08:36:00 -0000 [thread overview]
Message-ID: <20021022153602.5606.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/7133; it has been noted by GNATS.
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: dalej@gcc.gnu.org,dalej@gcc.gnu.org,dje@gcc.gnu.org,
gcc-bugs@gcc.gnu.org,gcc-prs@gcc.gnu.org,gcc-gnats@gcc.gnu.org
Cc: dalej@gcc.gnu.org,dje@gcc.gnu.org,gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org
Subject: Re: target/7133: PPC: unrecognizable insn
Date: Tue, 22 Oct 2002 17:26:53 +0200
At 00:01 22.10.2002, dalej@gcc.gnu.org wrote:
>Synopsis: PPC: unrecognizable insn
>
>Responsible-Changed-From-To: dje->dalej
>Responsible-Changed-By: dalej
>Responsible-Changed-When: Mon Oct 21 15:01:47 2002
>Responsible-Changed-Why:
> fixed it
>State-Changed-From-To: analyzed->closed
>State-Changed-By: dalej
>State-Changed-When: Mon Oct 21 15:01:47 2002
>State-Changed-Why:
> fixed it
>
>http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7133
Uhm, you shouldn't close a bug report unless it is fixed in the current
release branch too. This was a regression (otherwise it wouldn't have
"high" priority), closing it before applying the patch to the branch will
trick the release manager.
next reply other threads:[~2002-10-22 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 8:36 Franz Sirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 12:55 sirl
2002-10-24 10:19 dalej
2002-10-23 3:36 Franz Sirl
2002-10-22 10:06 Dale Johannesen
2002-10-21 15:01 dalej
2002-07-07 21:56 dje
2002-06-26 3:36 Franz.Sirl-kernel
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=20021022153602.5606.qmail@sources.redhat.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=dalej@gcc.gnu.org \
--cc=gcc-prs@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).