John Fine <johnsfine@xxxxxxxxxxx> writes: > Thanks for the information. I think I understand what you said about > the line number. Less so, what you said about statements comparing as > equal. I don't understand how that might fit into the process of > optimizing. The internal data structures built by the optimizer compared as equal even though their hash code were different. This has nothing much to do with your program, and has everything to do with the data structures built within gcc. > The problem isn't even consistent with perfectly identical (massive) > source code. Checking build logs, I found the same error happened > twice out of several times the identical source code was compiled. > Rerunning outside of the build system (but same source code and g++ > command) it didn't happen again. That is extremely weird. > Do any of the optimizations make decisions based on the available > physical ram of the system on which the compile is running? 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. Ian
