Kris Jurka [EMAIL PROTECTED] writes:
Gcc 4.3 has started to perform optimizations based on the denial of the
existence of signed overflow. Building CVS HEAD with gcc 4.3rc2 I get the
following warnings:
Hmm, I suspect that it's not so much that they're performing new
optimizations as that
On Mon, 10 Mar 2008, Tom Lane wrote:
I am wondering if these checks have been no-ops in Postgres builds done
with gcc 4.1 and up, and we're only just now being told about it.
Since gcc 4.2 supports -Wstrict-overflow, I rebuilt pg with that to see
what it's doing currently. I'm not sure
Kris Jurka [EMAIL PROTECTED] writes:
Gcc 4.3 has started to perform optimizations based on the denial of the
existence of signed overflow.
...
I don't understand the difference between -fwrapv and
-fno-strict-aliasing, but it seems we need at least one of them.
I don't see
A while back Tom Lane presented the potential problem with gcc signed
overflow handling, but now it's not just a theoretical problem.
http://archives.postgresql.org/pgsql-hackers/2005-12/msg00635.php
Gcc 4.3 has started to perform optimizations based on the denial of the
existence of signed
