Hi Pádraig, > * lib/vma-iter.c (vma_iterate_bsd): Mark parameters unused > on the stub variant.
We had this several times already: As a maintainer of a package that uses Gnulib, you should *not* be dictating which warnings are to occur in *.c of Gnulib. https://lists.gnu.org/archive/html/bug-gnulib/2023-08/msg00145.html https://lists.gnu.org/archive/html/bug-gnulib/2024-08/msg00202.html https://lists.gnu.org/archive/html/bug-gnulib/2024-10/msg00008.html https://lists.gnu.org/archive/html/bug-gnulib/2024-12/msg00139.html https://lists.gnu.org/archive/html/bug-gnulib/2025-01/msg00151.html https://lists.gnu.org/archive/html/bug-gnulib/2025-02/msg00015.html https://lists.gnu.org/archive/html/bug-gnulib/2025-05/msg00226.html This use of _GL_UNUSED is silly, because vma_iterate_bsd is _meant_ to have different implementations (depending on platform), and it is _normal_ in such situations that some implementations don't use the arguments that other implementations use. I don't want to litter the code with such annotations. Why is the mechanism that I put in place to protect Gnulib from warning-related demands not working? Is it '-flto' again? This one has been reported as a gcc bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80922 I don't want to have the code littered with annotations, when the origin is a gcc bug. Bruno
