On 11/17/07 09:16, Eric Botcazou wrote:
I'm still seeing the same failure on x86_64-unknown-linux-gnu, is this
going to get fixed?
You're not supposed to configure the compiler with --disable-checking as this
disables the internal assertions, use --enable-checking=release instead.
No, that's not correct. Configuring with --disable-checking is
perfectly reasonable in some circumstances. For instance, when testing
the effect of a patch without the assertion noise.
--disable-checking will also uncover heisenbugs masked by asserts, as it
seems to be this case.
Diego.
