Re: meson vs. llvm bitcode files - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: meson vs. llvm bitcode files
Date
Msg-id CAN4CZFMJgY98+e_XtmCe-kfbQrH_qaQ+ej4hdagX0DSE2tjbmw@mail.gmail.com
Whole thread
In response to Re: meson vs. llvm bitcode files  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: meson vs. llvm bitcode files
List pgsql-hackers
Everything seems to be properly working with the new version in my
tests, I only have a few minor comments:

+   <para>
+    When <productname>PostgreSQL</productname> is built with
+    <productname>Meson</productname>, it installs a
+    <literal>pkg-config</literal> file named
+    <literal>postgresql-&majorversion;-llvm-jit-bitcode.pc</literal>.  It is
+    used internally to emit <acronym>LLVM</acronym> <acronym>JIT</acronym>
+    bitcode for the server and for selected
+    <filename>contrib</filename> modules, and it collects the same
+    compilation flags that are used to build the server itself.
+   </para>

Do we want to install these pc files even with -Dllvm=disabled?

diff --git a/src/tools/irlink b/src/tools/irlink
new file mode 100644
index 00000000000..6a03e4f5695
--- /dev/null
+++ b/src/tools/irlink

Shouldn't this file committed as executable?

+import shutil
+import subprocess
+import sys

Is shutil and sys used in the script?



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: "David G. Johnston"
Date:
Subject: Re: implement CAST(expr AS type FORMAT 'template')