https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121547
--- Comment #5 from Alejandro Colomar <foss+...@alejandro-colomar.es> --- (In reply to Sam James from comment #3) > Not a bug, I think. -Wall enables -Warray-parameter too which brings the > warning. Is that something we want? Normally, some diagnostic flags implicitly enable others, but it is surprising that some diagnostic flag is required to enable others. Why not make -Warray-parameter implicitly trigger -Warray-bounds, but let -Warray-bounds be enough for itself?