From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] Support LLVM 7 |
Date: | 2018-09-16 07:48:34 |
Message-ID: | 20180916074833.GB4707@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: To Andres Freund 2018-09-12 <20180912210734(dot)GB5666(at)msg(dot)df7cb(dot)de>
> I plan to switch postgresql-11.deb to LLVM 7 over the next days
> because of the support for non-x86 architectures
I did an upload of postgresql-11 beta3 with llvm 7 enabled on the
architectures where it is available (or supposed to become available),
that is, on !alpha !hppa !hurd-i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !m68k !sh4.
There are two failures:
https://buildd.debian.org/status/logs.php?pkg=postgresql-11&ver=11~beta3-2
sparc64 fails with a lot of these in the log:
FATAL: fatal llvm error: Invalid data was encountered while parsing the file
powerpc (the old 32-bit variant) has a lot of "server closed the
connection unexpectedly" in the regression logs, and one SIGILL:
2018-09-15 10:49:25.052 UTC [26458] LOG: server process (PID 26527) was terminated by signal 4: Illegal instruction
2018-09-15 10:49:25.052 UTC [26458] DETAIL: Failed process was running: SELECT '' AS tf_12, BOOLTBL1.*, BOOLTBL2.*
FROM BOOLTBL1, BOOLTBL2
WHERE BOOLTBL2.f1 <> BOOLTBL1.f1;
2018-09-15 10:49:25.052 UTC [26458] LOG: terminating any other active server processes
Both smell more like LLVM bugs rather than PostgreSQL, so I guess we
can dub that a success. I'll disable JIT on these architectures for
the next upload.
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-09-16 08:19:37 | Re: Collation versioning |
Previous Message | Mark Kirkwood | 2018-09-16 04:00:31 | Re: Code of Conduct plan |