From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: JIT compiling with LLVM v12.2 |
Date: | 2018-03-21 20:09:58 |
Message-ID: | 20180321200958.6xtdggilzpgnz5ev@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2018-03-22 09:00:19 +1300, Thomas Munro wrote:
> On Thu, Mar 22, 2018 at 8:47 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > On 2018-03-21 20:06:49 +1300, Thomas Munro wrote:
> >> On Wed, Mar 21, 2018 at 4:07 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> >> > Indeed. I've pushed a rebased version now, that basically just fixes the
> >> > issue Thomas observed.
> >>
> >> I set up a 32 bit i386 virtual machine and installed Debian 9.4.
> >> Compiler warnings:
> >
> > Was that with a 64bit CPU and 32bit OS, or actually a 32bit CPU?
>
> 64 bit CPU, 32 bit OS. I didn't try Debian multi-arch i386 support on
> an amd64 system, but that's probably an easier way to do this if you
> already have one of those...
Ah, then I think I might know what happend. Does it start to work if you
replace the auto-detected cpu with "x86"? I think what might happen is
that it generates 64bit code, because of the detected CPU name.
Let me set up a chroot, in this case I should be able to emulate this
pretty easily...
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-03-21 20:31:12 | Re: JIT compiling with LLVM v12.2 |
Previous Message | Andres Freund | 2018-03-21 20:06:43 | Re: JIT compiling with LLVM v12.2 |