Re: internal compiler error: in avail_expr_eq, at tree-ssa-dom.c:2055

[John Fine <johnsfine at verizon dot net>]

I want to be sure I really understood you on that point.

The internal garbage collector is influenced by physical ram use by 
other processes?

This in not an issue of virtual memory limits in the current process (it 
is AMD64 and VIRT is under2GB).

This is not an issue of system wide commit level (the swap space is 
slightly larger than the VIRT total across all processes, and not all of 
that VIRT even needs one of physical ram or swap, and there is 8GB of 
physical ram).

But physical ram is somewhat low (the compiles each have slightly lower 
RES memory than the same compile would have if it were running alone and 
cache is much lower, so .hpp files are being reread rather than always 
found in cache).

Do you happen to know what method the internal garbage collector uses to 
ask about physical ram in order to be affected by it?

I understand how hard it would be to look for a bug that depends on 
garbage collector choices in a very big compile.  So I guess I should be 
very glad the compiler crashes rather than silently producing wrong 
results.  But I would like a better understanding myself of what 
influences compiler behavior.

Ian Lance Taylor wrote:
> No.  However, gcc's internal garbage collector does make such decisions.
> This is not supposed to affect the compiler's output, but of course if
> there is a bug it might.
>
>