On 9 November 2015 at 10:21, Paolo Bonzini <pbonz...@redhat.com> wrote: > Hmm, so the list is pretty short:
The good news is that my second bisect conclusively fingered the culprit for why the bug went away... > configure: disable FORTIFY_SOURCE under clang ...the bad news is it's because this patch inadvertently makes all non-fortify-source compiles be no-optimization (and we already knew the bug didn't repro in an unoptimized build). This also explains the weird behaviour in bisect: it was only when some later commit touched enough of the header files to force recompilation of whichever object file it is that's being problematic that the bug disappeared. thanks -- PMM
