Re: [PATCH 0/3] Work around icc miscompilation - Mailing list pgsql-hackers

From Xi Wang
Subject Re: [PATCH 0/3] Work around icc miscompilation
Date
Msg-id CAKU6vyZ9NnVdB46xtxWFYWHg2Syt+59fsA7+aCeXfTsP_uki6Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH 0/3] Work around icc miscompilation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
It depends on the context.  In the patches, `a' is known to be
non-negative, so `INT_MAX - a' cannot overflow.  If you ignore the
context and talk about the general case, then it can.

- xi

On Sat, Feb 23, 2013 at 12:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Stark <stark@mit.edu> writes:
>> He's changing things to do
>
>> if (INT_MAX - a > b)
>>   PG_THROW ("a+b would overflow")
>> else
>>   x=a+b;
>
>> Why would a smarter compiler be licensed to conclude that it can
>> optimize away anything? "INT_MAX-a > b" is always well defined.
>
> Really?  Can't "INT_MAX - a" overflow?
>
>                         regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH 0/3] Work around icc miscompilation
Next
From: Andrew Dunstan
Date:
Subject: Re: make: *** pg_xlogdump: No such file or directory. Stop.