Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1vR1xV-004c23-0Q
	for pgsql-hackers@arkaria.postgresql.org;
	Thu, 04 Dec 2025 05:32:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1vR1xT-000kDR-0k
	for pgsql-hackers@arkaria.postgresql.org;
	Thu, 04 Dec 2025 05:32:51 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vR1xS-000kDI-33
	for pgsql-hackers@lists.postgresql.org;
	Thu, 04 Dec 2025 05:32:51 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vR1xQ-0032jh-37
	for pgsql-hackers@lists.postgresql.org;
	Thu, 04 Dec 2025 05:32:50 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5B45Wlkw988387
	for <pgsql-hackers@lists.postgresql.org>; Thu, 4 Dec 2025 00:32:47 -0500
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
In-reply-to: <986485.1764825548@sss.pgh.pa.us>
References: <986485.1764825548@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Thu, 04 Dec 2025 00:19:08 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <988385.1764826367.1@sss.pgh.pa.us>
Date: Thu, 04 Dec 2025 00:32:47 -0500
Message-ID: <988386.1764826367@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/988386.1764826367%40sss.pgh.pa.us>
Precedence: bulk

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