Re: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT

Lists: pgsql-hackers
From: Pierre-Emmanuel André <postgresql(at)raveland(dot)org>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT
Date: 2018-05-24 19:47:27
Message-ID: 20180524194727.GA1391@coredump.raveland.priv
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hello,

I'm the maintainer of PostgreSQL on OpenBSD.
Today I tried the beta1 of PostgreSQL 11 on OpenBSD -current @amd64.

Without JIT, everything works fine.

When i enable JIT, regress tests fail with this error :

indexing ... FAILED (test process exited with exit code 2)

llvm-config --version gives me : 6.0.0
You will find in attachment the complete log of the failure (regressions.diff).
At the end, there is these 2 lines :

! WARNING: failed to resolve name __guard_local
! FATAL: fatal llvm error: Program used external function '__guard_local' which could not be resolved!

Any ideas ?

Thanks.
Regards,

Attachment Content-Type Size
regression.diffs text/plain 10.4 KB

From: Andres Freund <andres(at)anarazel(dot)de>
To: Pierre-Emmanuel André <postgresql(at)raveland(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT
Date: 2018-05-24 20:03:00
Message-ID: 20180524200300.ttjmezir5utjzafg@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi,

On 2018-05-24 21:47:27 +0200, Pierre-Emmanuel André wrote:
> Hello,
>
> I'm the maintainer of PostgreSQL on OpenBSD.
> Today I tried the beta1 of PostgreSQL 11 on OpenBSD -current @amd64.
>
> Without JIT, everything works fine.
>
> When i enable JIT, regress tests fail with this error :

Thanks for the report.

> indexing ... FAILED (test process exited with exit code 2)
>
>
> llvm-config --version gives me : 6.0.0
> You will find in attachment the complete log of the failure (regressions.diff).
> At the end, there is these 2 lines :
>

> ! WARNING: failed to resolve name __guard_local
> ! FATAL: fatal llvm error: Program used external function '__guard_local' which could not be resolved!

__guard_local is part of stack protector logic. I'm not clear whether
the issue is that the different parts of the build used different flags,
or whether the symbol is hidden at runtime. Could you share your
configure invocation and config.log output?

Greetings,

Andres Freund


From: Pierre-Emmanuel André <postgresql(at)raveland(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT
Date: 2018-05-25 12:37:52
Message-ID: 20180525123751.zkow75jqtii2xxk4@digipea.digitick.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, May 24, 2018 at 01:03:00PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-05-24 21:47:27 +0200, Pierre-Emmanuel André wrote:
> > Hello,
> >
> > I'm the maintainer of PostgreSQL on OpenBSD.
> > Today I tried the beta1 of PostgreSQL 11 on OpenBSD -current @amd64.
> >
> > Without JIT, everything works fine.
> >
> > When i enable JIT, regress tests fail with this error :
>
> Thanks for the report.
>
>
> > indexing ... FAILED (test process exited with exit code 2)
> >
> >
> > llvm-config --version gives me : 6.0.0
> > You will find in attachment the complete log of the failure (regressions.diff).
> > At the end, there is these 2 lines :
> >
>
> > ! WARNING: failed to resolve name __guard_local
> > ! FATAL: fatal llvm error: Program used external function '__guard_local' which could not be resolved!
>
> __guard_local is part of stack protector logic. I'm not clear whether
> the issue is that the different parts of the build used different flags,
> or whether the symbol is hidden at runtime. Could you share your
> configure invocation and config.log output?
>

Yes sure. The configure invocation :

$ ./configure --disable-rpath --with-openssl=/usr --with-bsd-auth --with-perl --with-python --with-pam=no --with-uuid=bsd --enable-integer-datetimes --includedir=/usr/local/include/postgresql --datadir=/usr/local/share/postgresql --docdir=/usr/local/share/doc/postgresql --with-includes= --with-libraries=/usr/local/lib --with-system-tzdata=/usr/share/zoneinfo --with-openssl --with-libxml --with-llvm --disable-thread-safety --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/local/man --infodir=/usr/local/info --localstatedir=/var --disable-silent-rules --disable-gtk-doc

The config.log is in attachment.

Regards,

Attachment Content-Type Size
config.log text/plain 489.8 KB

From: Pierre-Emmanuel André <postgresql(at)raveland(dot)org>
To:
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL 11 beta1 : regressions failed on OpenBSD with JIT
Date: 2018-06-06 07:49:24
Message-ID: 20180606074924.t353mab2pf4lwaby@digipea.digitick.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, May 25, 2018 at 02:37:52PM +0200, Pierre-Emmanuel André wrote:
> On Thu, May 24, 2018 at 01:03:00PM -0700, Andres Freund wrote:
> > Hi,
> >
> > On 2018-05-24 21:47:27 +0200, Pierre-Emmanuel André wrote:
> > > Hello,
> > >
> > > I'm the maintainer of PostgreSQL on OpenBSD.
> > > Today I tried the beta1 of PostgreSQL 11 on OpenBSD -current @amd64.
> > >
> > > Without JIT, everything works fine.
> > >
> > > When i enable JIT, regress tests fail with this error :
> >
> > Thanks for the report.
> >
> >
> > > indexing ... FAILED (test process exited with exit code 2)
> > >
> > >
> > > llvm-config --version gives me : 6.0.0
> > > You will find in attachment the complete log of the failure (regressions.diff).
> > > At the end, there is these 2 lines :
> > >
> >
> > > ! WARNING: failed to resolve name __guard_local
> > > ! FATAL: fatal llvm error: Program used external function '__guard_local' which could not be resolved!
> >
> > __guard_local is part of stack protector logic. I'm not clear whether
> > the issue is that the different parts of the build used different flags,
> > or whether the symbol is hidden at runtime. Could you share your
> > configure invocation and config.log output?
> >
>
> Yes sure. The configure invocation :
>
> $ ./configure --disable-rpath --with-openssl=/usr --with-bsd-auth --with-perl --with-python --with-pam=no --with-uuid=bsd --enable-integer-datetimes --includedir=/usr/local/include/postgresql --datadir=/usr/local/share/postgresql --docdir=/usr/local/share/doc/postgresql --with-includes= --with-libraries=/usr/local/lib --with-system-tzdata=/usr/share/zoneinfo --with-openssl --with-libxml --with-llvm --disable-thread-safety --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/local/man --infodir=/usr/local/info --localstatedir=/var --disable-silent-rules --disable-gtk-doc
>
> The config.log is in attachment.
>
[...]

Hello,

Any news ? Except JIT, PostgreSQL 11beta1 works fine on OpenBSD -current.
Regards,