This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PCH and exec-shield...
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>, Mark Mitchell <mark at codesourcery dot com>, David Edelsohn <dje at watson dot ibm dot com>, law at redhat dot com, Eric Christopher <echristo at redhat dot com>, David Daney <ddaney at avtrex dot com>, gcc at gcc dot gnu dot org
- Date: 16 Mar 2004 21:51:28 -0500
- Subject: Re: PCH and exec-shield...
- References: <B24DD01C-77B2-11D8-A9C8-003065A77310@apple.com>
Mike Stump <mrs@apple.com> writes:
> On Tuesday, March 16, 2004, at 03:50 PM, Zack Weinberg wrote:
> > To ask a tangential question, if (as presently implemented) PCH has to
> > reload data structures at the original address, why is there a problem
> > with hashing pointers?
>
> We swizzle on PCH write. PCH write can be amortized across multiple
> uses better, also, during writing, memory is hot. During load, we
> could have to bring in (from disk/network) and COW it.
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.
So I still don't understand why we can't hash on pointer values.
Ian