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.94.2) (envelope-from ) id 1tuwV2-00ElWZ-Hn for pgsql-committers@arkaria.postgresql.org; Wed, 19 Mar 2025 16:42:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tuwV0-007mMk-Er for pgsql-committers@arkaria.postgresql.org; Wed, 19 Mar 2025 16:42:34 +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.94.2) (envelope-from ) id 1tuwUz-007mLa-RV for pgsql-committers@lists.postgresql.org; Wed, 19 Mar 2025 16:42:33 +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 ) id 1tuwUw-003nCr-1D for pgsql-committers@lists.postgresql.org; Wed, 19 Mar 2025 16:42:33 +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 52JGgS3O713811; Wed, 19 Mar 2025 12:42:28 -0400 From: Tom Lane To: Andres Freund cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: aio: Add core asynchronous I/O infrastructure In-reply-to: References: <93029.1742310216@sss.pgh.pa.us> <95354.1742311575@sss.pgh.pa.us> Comments: In-reply-to Andres Freund message dated "Wed, 19 Mar 2025 10:29:19 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <713809.1742402548.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 19 Mar 2025 12:42:28 -0400 Message-ID: <713810.1742402548@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > On 2025-03-18 11:26:15 -0400, Tom Lane wrote: >> Well, if we don't want to fix it I can just adjust my warning-scraping >> script to ignore these. Let's wait a bit and see if any newer >> compilers warn similarly before deciding. > FWIW, adding a few casts does silence the warnings, at least on clang-3.= 9, > which I had around. As of now, the only BF members showing these warnings are ayu (clang version 4.0.1-10~deb9u2), batfish (clang version 5.0.0-3~16.04.1), and demoiselle (clang version 5.0.1). None of those seem like versions that anyone would use for code development anymore (clang 6.0 was released in March 2018), so I'm not feeling like these warnings are important to silence. Let's just ignore them. > But there also are other warnings on that compiler, mainly stuff like: > ../../home/andres/src/postgresql/src/interfaces/libpq/fe-auth-oauth-curl= .c:1437:28: warning: suggest braces around initialization of subobject [-W= missing-braces] > struct itimerspec spec =3D {0}; And even more so that, if it's so old it's not even in the buildfarm anymore. I do care about -Wmissing-braces on a version developers might use, but ... regards, tom lane