On 08/06/2018 05:59 PM, Martin Sebor wrote: >>> But as I said, far more essential than the optimization is >>> the ability to detect these invalid access (both reads and >>> writes), such as in: >> >> The essential thing is to not introduce latent wrong code issues >> because you exploit C language constraints that are not preserved by >> GIMPLE transforms because they are not constraints in the GIMPLE IL >> _WHICH_ _IS_ _NOT_ _C_. > > You misunderstood my point: I'm saying "if you must, disable > the strlen optimization but please don't compromise the bug > detection." And to be clear, you should be involved in that process.
Note if fixing the codegen issues loses warnings and restoring the warnings is a major effort, then the warnings may have to regress. jeff
