Re: [PATCH 0/3] Work around icc miscompilation

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Xi Wang <xi(dot)wang(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [PATCH 0/3] Work around icc miscompilation
Date: 2013-01-24 10:02:09
Message-ID: 510106A1.6080507@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-01-24 10:26:36 Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]
Previous Message Xi Wang 2013-01-24 09:41:25 [PATCH 3/3] Fix overflow checking in repeat()