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

From Heikki Linnakangas
Subject Re: [PATCH 0/3] Work around icc miscompilation
Date
Msg-id 510106A1.6080507@vmware.com
Whole thread Raw
In response to [PATCH 0/3] Work around icc miscompilation  (Xi Wang <xi.wang@gmail.com>)
Responses Re: [PATCH 0/3] Work around icc miscompilation
List pgsql-hackers
On 24.01.2013 11:33, Xi Wang wrote:
> I'm sending three smaller patches for review, which try to fix icc
> and pathscale (mis)compilation problems described in my last email.

These patches look ok at a quick glance, but how do we ensure this kind 
of problems don't crop back again in the future? Does icc give a warning 
about these? Do we have a buildfarm animal that produces the warnings?

If we fix these, can we stop using -frapv on gcc? Is there any way to 
get gcc to warn about these?

- Heikki



pgsql-hackers by date:

Previous
From: Xi Wang
Date:
Subject: [PATCH 3/3] Fix overflow checking in repeat()
Next
From: Amit Kapila
Date:
Subject: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]