public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/4520: cselib.c hash_rtx incorrectly hashes based on rtx address
Date: Sat, 21 Dec 2002 23:06:00 -0000 [thread overview]
Message-ID: <20021222070601.17785.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/4520; it has been noted by GNATS.
From: Geoff Keating <geoffk@geoffk.org>
To: dje@watson.ibm.com
Cc: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
john@feith.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: other/4520: cselib.c hash_rtx incorrectly hashes based on rtx address
Date: Sat, 21 Dec 2002 22:56:59 -0800
> Cc: Geoff Keating <geoffk@geoffk.org>
> Date: Sat, 21 Dec 2002 13:22:13 -0500
> From: David Edelsohn <dje@watson.ibm.com>
> X-OriginalArrivalTime: 21 Dec 2002 18:22:33.0209 (UTC) FILETIME=[EE029E90:01C2A91D]
>
> >>>>> bangerth writes:
>
> Wolfgang> David, you probably have more insight into these things than
> Wolfgang> me, but I know that some of these address-hashing things
> Wolfgang> have been purged. Is this particular report still valid?
>
> As far as I can tell, the incorrect hashing of addresses of
> LABEL_REFS and SYMBOL_REFS in cselib.c:hash_rtx() has not been corrected.
> The failure is dormant, but I am not sure how it affects PCH restore
> state.
cselib.c isn't active when PCH files are saved, so nothing in cselib.c
affects PCH.
--
- Geoffrey Keating <geoffk@geoffk.org>
next reply other threads:[~2002-12-22 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 23:06 Geoff Keating [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-21 10:29 bangerth
2002-12-21 10:26 David Edelsohn
2002-12-21 9:04 bangerth
2001-10-10 7:56 dje
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=20021222070601.17785.qmail@sources.redhat.com \
--to=geoffk@geoffk.org \
--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).