From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: icc vs. gcc-style asm blocks ... maybe the twain can meet? |
Date: | 2015-09-01 15:05:58 |
Message-ID: | CA+TgmoZi6nJQ-QQCPQpv_1Vcf3biLs6gW-WqZRy1cKw84hGvoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 1, 2015 at 10:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sun, Aug 30, 2015 at 7:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Hmm ... wait a second. The main collection of asm blocks in s_lock.h
>>> believes that Intel's compiler will take gcc-style asm without any help:
>
>> The 2005 block seems to have been the result of this thread:
>> http://www.postgresql.org/message-id/flat/200503090429(dot)j294TlG10498(at)candle(dot)pha(dot)pa(dot)us
>> That thread seems pretty clear about asm() not working in that
>> poster's environment.
>
> See followups --- the true story is that icc can do asm blocks on
> x86[_64], but not ia64. I've now documented this accurately, and
> fixed various places that were confused about it.
Thanks.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2015-09-01 15:18:38 | Re: Horizontal scalability/sharding |
Previous Message | Robert Haas | 2015-09-01 15:05:37 | Re: Potential GIN vacuum bug |