Re: JIT works only partially with meson build?

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: JIT works only partially with meson build?
Date: 2025-10-01 13:25:51
Message-ID: 5a88920da32b910fac64608980d8fe690a14d7d7.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2025-09-30 at 22:31 +0900, Yugo Nagata wrote:
> > You used the <option> tag, which I believe is correct, but the surrounding
> > code uses <literal>. I don't think it renders differently, but I think it
> > would be good to use the same tag. I suggest that you change the
> > surrounding code to use <option> as well.
>
> Agreed. I fixed it to use <option>, as well as in other place where I think
> <option> is appropriate. Please find the attached patch.

I'll mark it "eeady for committer". A committer can decide whether to apply
this to HEAD or not. I probably would, and revert it if PostgreSQL + Meson +
Windows learns to produce bitcode.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniil Davydov 2025-10-01 13:30:38 Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION
Previous Message Robert Haas 2025-10-01 12:40:26 Re: [PATCH] Fix pg_rewind false positives caused by shutdown-only WAL