public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Jessica Han" <jessica@cup.hp.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/4351: gcc internal error when compiling on HP-UX 11.00
Date: Tue, 11 Dec 2001 16:56:00 -0000 [thread overview]
Message-ID: <20011212005601.8690.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/4351; it has been noted by GNATS.
From: "Jessica Han" <jessica@cup.hp.com>
To: <rodrigc@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<harri.pasanen@trema.com>, <nobody@gcc.gnu.org>
Cc:
Subject: RE: c++/4351: gcc internal error when compiling on HP-UX 11.00
Date: Tue, 11 Dec 2001 16:50:31 -0800
The patch fixed the compile time error, Thanks Richard.
-----Original Message-----
From: rodrigc@gcc.gnu.org [mailto:rodrigc@gcc.gnu.org]
Sent: Tuesday, December 11, 2001 4:44 PM
To: gcc-bugs@gcc.gnu.org; gcc-gnats@gcc.gnu.org; gcc-prs@gcc.gnu.org;
harri.pasanen@trema.com; jessica@cup.hp.com; rodrigc@gcc.gnu.org;
nobody@gcc.gnu.org
Subject: Re: c++/4351: gcc internal error when compiling on HP-UX 11.00
Synopsis: gcc internal error when compiling on HP-UX 11.00
State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Tue Dec 11 16:43:34 2001
State-Changed-Why:
Can you try this patch, supplied
by Richard Henderson:
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg01310.html
If you can test it under HPUX then I
can close PR 4351.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4351&databa
se=gcc
next reply other threads:[~2001-12-12 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 16:56 Jessica Han [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 19:56 rodrigc
2001-12-11 19:45 rodrigc
2001-12-11 16:46 rodrigc
2001-12-11 16:43 rodrigc
2001-09-18 9:06 harri.pasanen
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=20011212005601.8690.qmail@sources.redhat.com \
--to=jessica@cup.hp.com \
--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).