From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE
Date: Thu, 04 Dec 2025 00:32:47 -0500
Message-ID: <988386.1764826367@sss.pgh.pa.us> (raw)
In-Reply-To: <986485.1764825548@sss.pgh.pa.us>
References: <986485.1764825548@sss.pgh.pa.us>
I wrote:
> Adding to my confusion, I do not see these warnings on a local
> RHEL9 machine, which ought to be pretty equivalent to CentOS 9.
Oh! I see part of the story: I was testing that with gcc.
If I switch to clang (version 20.1.8 here), then I see that
we pick "__syslog__" and then these complaints appear.
So why isn't clang being bug-compatible with gcc on the
names of printf archetypes? They're certainly pretty
slavish about that on most other topics.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE
In-Reply-To: <988386.1764826367@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox