In article <[EMAIL PROTECTED]> you write: >I don't think doing any of both is a good idea. Authors of the affected >programs should adjust their makefiles instead - after all, the much more >often reported problems are with -fstrict-aliasing, and this one also doesn't >get any special treatment by autoconf. Even though -fno-strict-aliasing >-fwrapv >would be a valid, more forgiving default. Also as ever, -O2 is what get's >the most testing, so you are going to more likely run into compiler bugs >with -fwrapv.
As a measure point, in the OpenBSD project, we have disabled -fstrict-aliasing by default. The documentation to gcc local to our systems duly notes this departure from the canonical release. We expect to keep it that way about forever. If/when we update to a version wher -fwrapv becomes an issue, we'll probably do the same with it. Specifically, because we value reliability over speed and strict standard conformance...
