Bootstrap failure due to GC / PCH memory corruption

[Zack Weinberg]

Geoff Keating <geoffk@geoffk.org> writes:

>> I also suggest that you find out what these objects are that are
>> larger than a page.  To first order there shouldn't be any.  The only
>> thing I've ever seen allocate more than a page at once from GC arena
>> was a giant dense switch statement.
>
> There are many such objects, for instance the identifier hash table is
> a minimum 200k.

Since when is the identifier hash table allocated with ggc_alloc?
ht_create uses xmalloc.

I should point out that ggc-page.c is heinously inefficient when
allocating objects larger than a single page.  This is tolerable
as long as we don't allocate very many such objects, but if we are
now allocating lots of them, it needs to be fixed.

zw