public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9138: New C++ parser regression on mips-irix6 with g++.jason/thunk1.C (and thunk2.C/thunk3.C)
Date: Fri, 03 Jan 2003 15:36:00 -0000 [thread overview]
Message-ID: <20030103153601.5929.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9138; it has been noted by GNATS.
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org,
gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, mark@codesourcery.com,
nobody@gcc.gnu.org
Cc:
Subject: Re: c++/9138: New C++ parser regression on mips-irix6 with g++.jason/thunk1.C (and thunk2.C/thunk3.C)
Date: Fri, 3 Jan 2003 10:31:09 -0500 (EST)
> From: ehrhardt@mathematik.uni-ulm.de
>
> Synopsis: New C++ parser regression on mips-irix6 with g++.jason/thunk1.C (and thunk2.C/thunk3.C)
>
> State-Changed-From-To: open->feedback
> State-Changed-By: cae
> State-Changed-When: Fri Jan 3 02:29:42 2003
> State-Changed-Why:
> This discussion about this PR has been picked up by GNATS as new PRs:
> PR 9145 and PR 9148. This discussion indicates that this PR is fixed.
> Is this true?
Why does GNATS keep opening new PRs? What is triggering that?
On the original bug, Mark wrote a patch for me to test. I verified it
works on irix6, but he has not yet installed it. When he does, I will
close the PR.
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next reply other threads:[~2003-01-03 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 15:36 Kaveh R. Ghazi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 16:42 ghazi
2003-01-03 10:29 ehrhardt
2003-01-02 17:36 ghazi
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=20030103153601.5929.qmail@sources.redhat.com \
--to=ghazi@caip.rutgers.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).