On 14 Sep 2014, at 19:27, Dimitry Andric <[email protected]> wrote: ... > In any case, I have now narrowed it down to gcc/tree.c, which is not a > very small file, and which is changed very often upstream, sometimes > almost daily. > > So I will see if I can reproduce it with gcc trunk first, and if that > turns out to be good, I will bisect to find the commit that fixes it. > > If trunk is also not good, the rabbit hole goes a bit deeper...
And deeper it goes: gcc trunk does not crash, *unless* I change the file gcc/DEV-PHASE to contain the string "prerelease" instead of the default "experimental". Then gcc trunk crashes in an identical fashion to the gcc 4.8 branch, or gcc 4.8.2 release! Anybody have an idea what kind of magic in gcc is changed, when this DEV-PHASE file is altered? Some debug code or internal assertion checking might be turned on or off? -Dimitry
signature.asc
Description: Message signed with OpenPGP using GPGMail
