This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/48978] excessive hash table allocation for large lto build
- From: "andi-gcc at firstfloor dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 12 May 2011 16:34:13 +0000
- Subject: [Bug lto/48978] excessive hash table allocation for large lto build
- Auto-submitted: auto-generated
- References: <bug-48978-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48978
--- Comment #2 from Andi Kleen <andi-gcc at firstfloor dot org> 2011-05-12 16:16:19 UTC ---
I will try.
BTW this was a much larger test case (allyesconfig), the tarball I sent you
is a much more limited config.
Normally noone uses allyesconfig kernels (they barely boot), but they
are a good stress tester for the compiler.
Still I suspect the hash table expansion algorithms are not optimal.
If you're already in the GB range you shouldn't be doubling anymore...