Re: JIT compiling with LLVM v11

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>
Subject: Re: JIT compiling with LLVM v11
Date: 2018-03-08 20:31:19
Message-ID: CAEepm=2KPYMP1tGqd4ASaRB6bp9b2k=vnESWg+t8HX-3cR6i=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 9, 2018 at 9:12 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Or even in core LLVM, which has this nice comment:
>
> // If user asked for the 'native' CPU, we need to autodetect features.
> // This is necessary for x86 where the CPU might not support all the
> // features the autodetected CPU name lists in the target. For example,
> // not all Sandybridge processors support AVX.
> if (MCPU == "native") {
>
> which pretty much describes the issue you're apparently hitting.
>
> I've pushed an attempted fix (needs a comment, but works here).

=======================
All 186 tests passed.
=======================

That did the trick. Thanks!

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Wildish 2018-03-08 21:11:58 Re: Implementing SQL ASSERTION
Previous Message Andres Freund 2018-03-08 20:26:53 Re: RFC: Add 'taint' field to pg_control.