Nicholas Clark wrote:
I think the compiler is to blame. It only happens when compiling the code in the computed goto core. I *suspect* the compiler backs out of a lot of analysis and transforms that it would normally do due to the complexity of analysing code using computed goto, since the problem code compiled just fine outside of the computed goto core without the patch.Do the structures actually overlap, or is this necessary band aid for a subtly broken compiler?
Jonathan
