public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gary Hade <garyhade@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5892: ICE in gen_nop_type during 2.4.17 ia64 kernel build
Date: Mon, 18 Mar 2002 11:26:00 -0000 [thread overview]
Message-ID: <20020318192603.26866.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/5892; it has been noted by GNATS.
From: Gary Hade <garyhade@us.ibm.com>
To: rodrigc@gcc.gnu.org, garyhade@us.ibm.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: optimization/5892: ICE in gen_nop_type during 2.4.17 ia64 kernel build
Date: Mon, 18 Mar 2002 11:24:32 -0800
On Sat, Mar 16, 2002 at 03:52:39AM -0000, rodrigc@gcc.gnu.org wrote:
> Synopsis: ICE in gen_nop_type during 2.4.17 ia64 kernel build
>
> State-Changed-From-To: analyzed->feedback
> State-Changed-By: rodrigc
> State-Changed-When: Fri Mar 15 19:52:39 2002
> State-Changed-Why:
> Can you verify that this patch fixes the problem:
> http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00705.html
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5892
Yes, the patch fixes the problem. I verified by building the
2.4.17 and 2.4.18 kernels using a gcc built from source updated
on 3/14 from the CVS gcc-3_1-branch which contained the patch
mentioned in http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00705.html.
No ICEs were encountered.
Thanks,
Gary
--
Gary Hade
IBM Linux Technology Center
503-578-4503 IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc
next reply other threads:[~2002-03-18 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 11:26 Gary Hade [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 13:07 rodrigc
2002-03-15 19:52 rodrigc
2002-03-09 6:00 jakub
2002-03-08 14:06 garyhade
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=20020318192603.26866.qmail@sources.redhat.com \
--to=garyhade@us.ibm.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).