From: Mike Stump <mrs@apple.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
Mark Mitchell <mark@codesourcery.com>,
David Edelsohn <dje@watson.ibm.com>,
law@redhat.com, Eric Christopher <echristo@redhat.com>,
David Daney <ddaney@avtrex.com>,
gcc@gcc.gnu.org
Subject: Re: PCH and exec-shield...
Date: Wed, 17 Mar 2004 18:49:00 -0000 [thread overview]
Message-ID: <877D1AFA-7843-11D8-B054-003065A77310@apple.com> (raw)
In-Reply-To: <m3ad2grxsf.fsf@gossamer.airs.com>
On Tuesday, March 16, 2004, at 06:51 PM, Ian Lance Taylor wrote:
> On PCH write, gcc swizzles pointers and also copies the hash tables to
> the PCH address. It seems to me that gcc could rehash the pointer
> values while copying the hash tables.
Minor nit, I don't believe we copy. We merely edit in place and write.
But yes, I suspect that could be done.
> So I still don't understand why we can't hash on pointer values.
I don't think it was meant that it is impossible, but that more code
would need to be written. Merely changing to use address, would be
wrong. Doing this and fixing it so that it would work fully, would be
fine.
next prev parent reply other threads:[~2004-03-17 18:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 19:02 David Daney
2004-03-02 19:05 ` Eric Christopher
2004-03-02 19:22 ` law
2004-03-02 19:55 ` Jakub Jelinek
2004-03-02 19:59 ` Ian Lance Taylor
2004-03-02 20:09 ` Jakub Jelinek
2004-03-02 20:17 ` Ian Lance Taylor
2004-03-02 21:00 ` Geoff Keating
2004-03-08 21:04 ` Mark Mitchell
2004-03-08 21:13 ` Ian Lance Taylor
2004-03-08 21:34 ` Mark Mitchell
2004-03-16 3:36 ` Mike Stump
2004-03-16 4:15 ` David Edelsohn
2004-03-16 22:17 ` Mike Stump
2004-03-16 22:37 ` Mark Mitchell
2004-03-16 23:55 ` Zack Weinberg
2004-03-17 1:49 ` Mike Stump
2004-03-17 2:55 ` Ian Lance Taylor
2004-03-17 18:49 ` Mike Stump [this message]
2004-03-21 18:14 ` Hans-Peter Nilsson
2004-03-21 19:29 ` Zack Weinberg
2004-03-16 4:34 ` Mark Mitchell
2004-03-02 21:01 ` Geoff Keating
2004-03-02 19:25 ` Giovanni Bajo
2004-03-03 4:04 ` Ian Lance Taylor
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=877D1AFA-7843-11D8-B054-003065A77310@apple.com \
--to=mrs@apple.com \
--cc=ddaney@avtrex.com \
--cc=dje@watson.ibm.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=law@redhat.com \
--cc=mark@codesourcery.com \
--cc=zack@codesourcery.com \
/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).