[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib-manywarnings: Enable -Wzero-as-null-pointer-constant
From: |
Simon Josefsson |
Subject: |
Re: gnulib-manywarnings: Enable -Wzero-as-null-pointer-constant |
Date: |
Thu, 14 Nov 2024 09:26:59 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Bruno Haible via Gnulib discussion list <bug-gnulib@gnu.org> writes:
> Hi Alejandro,
>
>> We're planning a path for deprecation of 0 as a null pointer constant,
>> in favor of NULL
>
> +1
+1
> For reference, we discussed the use of nullptr in Gnulib [1][2] in the past.
>
>> As a first step, Joseph proposed adding it into gnulib's manywarnings.
>> Does it sound good to you?
>
> Yes. Usually we augment the manywarnings module right after a new GCC
> release, but there is no problem adding a new warning that still only
> exists in GCC snapshots.
>
> Let me
> - build a GCC snapshot locally,
I have been using the following GCC container images for CI/CD testing
of different packages with good results over the years:
https://hub.docker.com/_/gcc/
Are there gcc pre-test container images available too? If you publish
GCC 15.x container images it would be relatively easy to use them in a
CI/CD pipeline to test if it behaves well on various packages.
For similar purpose, I've been using the following clang container for
testing. They provide both a 'latest' tag and the 'dev' tag for the
nightly builds: https://hub.docker.com/r/silkeh/clang
/Simon
> - see how this new warning behaves on the Gnulib source code
> and some other packages (inetutils comes to mind),
> - then tell you about the results.
>
> Bruno
>
> [1] https://lists.gnu.org/archive/html/bug-gnulib/2023-02/msg00029.html
> [2] https://lists.gnu.org/archive/html/bug-gnulib/2023-02/msg00031.html
>
>
>
>
>
signature.asc
Description: PGP signature