GitLab

Bugzilla Link	542
Created on	Aug 05, 2009 00:16
Resolution	FIXED
Resolved on	Sep 27, 2009 19:22
Version	1.00beta
OS	Linux
Architecture	PC

Extended Description

I am unable to build the stdlib on a 4GB machine; the thing
runs out of memory. Memory use grows steadily during SAACYC, but I can't see
anything obvious in the way of corruption with memcheck or treecheck during
those phases. I noted this:
1. Turning off most optimizations let the compile complete.
2. The SAACYC optimization phases are spending most
   of their time here, based on eyeballing -v4 output:
       Eliminating type variables ...
       Eliminating bottom types ...
3.isaa2 produces a LOT of -d memcheck errors, but it is only invoked
  once, so I don't see that it can be the problem.
4. I did not see anything obvious in -b11:xxx output, such as
   multiple copies of same value being computed. etc.
5. I'm running valgrind on it now, but it's taking a wee bit of time.