> 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.
Not sure what you call the "assertion noise", (reasonable) assertions in a compiler are a feature, --disable-checking should not be advertised since all the assertions are now predicated on at least --enabled-checking=release. That being said, if there is a bug, I agree that we should try and fix it. -- Eric Botcazou
