Re: Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE
Date: 2025-12-05 08:51:53
Message-ID: 2910CE7A-62FE-4969-AF8F-E198EF0E1DDA@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Dec 2025, at 19:01, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> On the other hand, aligning the C++ compiler with the C compiler
> is likely to avoid other problems, so maybe it's better to focus
> on making that happen. I'm not sure how we'd do that automatically
> though.

It sounds pretty complicated to, with confidence, automatically detect this.
Maybe documenting that it's highly recommended to use matching C and C++
compilers is enough rather than spend cycles for every configure on a check
which may be susceptible to false negatives?

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Svetlana Derevyanko 2025-12-05 08:53:21 Strict functions with variadic "any" argument bug
Previous Message Bilal Yavuz 2025-12-05 07:50:25 Re: Improve error reporting in 027_stream_regress test