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 ) id 1w9rMV-001pey-35 for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 21:19:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9rMU-00C7oh-1N for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 21:19:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9rMU-00C7oZ-0W for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 21:19:58 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w9rMS-00000000uyj-2uv9 for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 21:19:57 +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 636LJpfS1912639; Mon, 6 Apr 2026 17:19:52 -0400 From: Tom Lane To: Peter Eisentraut cc: Bertrand Drouvot , pgsql-hackers@lists.postgresql.org Subject: Re: Enable -Wstrict-prototypes and -Wold-style-definition by default In-reply-to: References: <44885d54-0376-46b3-b574-59e0e3098580@eisentraut.org> <4ab608af-2f90-47d8-88a5-6329f6630fff@eisentraut.org> Comments: In-reply-to Peter Eisentraut message dated "Fri, 27 Mar 2026 08:38:45 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1912637.1775510391.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 06 Apr 2026 17:19:51 -0400 Message-ID: <1912638.1775510391@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > The first three patches have been committed. b4a132022 has had some not-so-desirable effects in the buildfarm: drongo and hoatzin are each spewing a couple dozen repetitive warnings about every bison-generated header file, eg src/backend/bootstrap/bootparse.h(111): warning C4255: 'boot_yyparse': no = function prototype given: converting '()' to '(void)' Both of those machines are using bison 2.7, which is pretty old and evidently isn't careful about generating complete prototypes. I'm not sure if there's anything to be done about this, except perhaps nag the animals' owners to find a newer bison somewhere. We could revert b4a132022, but then we might miss valid warnings about such issues in Windows-only code. regards, tom lane