On Sat, Jul 13, 2024 at 12:16 AM Bruno Haible <br...@clisp.org> wrote: > I wrote: > > so I can know why the CI did not report it within three weeks > > That was because the compilation error occurred only with clang 18, > which was released in March 2024 and is therefore not yet present > in the *BSD distros. > > In the last two years, I got the feeling that clang is adopting new > ISO C features more quickly than GCC (seen with the K&R prototypes > removal in clang 16, now with ckd_add in clang 18). So, would it > make sense to do a CI build with the newest released clang version? > > In contrast, a CI build with the newest released gcc version seems > less urgent, since > - Fedora jumps on the newest gcc quickly, > - gcc is not so frequently ahead of clang regarding ISO C language > features. > Right? > > Opinions?
It feels like a good thing to do, but will come with some cost: I have the impression that relatively few GNU projects use clang (and esp clang 18), so this testing is likely to expose more "issues". However, a more diverse set of compilers/warnings may expose real problems in our code sooner.
