From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: aio: Add core asynchronous I/O infrastructure |
Date: | 2025-03-19 14:29:19 |
Message-ID: | a54pqocps46awa4b2tlwmrjz5k3b3jastg5py6thtnqtlr2ksy@notafhjwiuec |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Hi,
On 2025-03-18 11:26:15 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I wonder if we should instead either ask those buildfarm animals to be
> > disabled or have the warning manually disabled. I don't think it's a good
> > investment on our part to work towards warning cleanliness on clang 4 and 5,
> > on distros from 2017 and and 2018 respectively.
>
> 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.
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 [-Wmissing-braces]
struct itimerspec spec = {0};
I lean towards not fixing this stuff, but if you would like me to, I can.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-03-19 16:42:28 | Re: pgsql: aio: Add core asynchronous I/O infrastructure |
Previous Message | Andres Freund | 2025-03-19 13:04:30 | pgsql: meson: Flush stdout in testwrap |