On Fri, 12 Oct 2012, Masanobu SAITOH wrote:
One of (serious) problem that we can't use -Wstrict-overflow by default is that gcc sometimes misundestand it :-< How should we use it?
Do you have an example where gcc does the wrong thing with -Wstrict-overflow? (The example in your message, which I am not quoting here, showed gcc doing the right thing: that is, drawing attention to a case where the program invoked undefined behaviour.)
--apb (Alan Barrett)