[PATCH 1/5] manywarnings: update C warnings for GCC 15

@@ -1,3 +1,13 @@ +2025-04-17 Paul Eggert + + manywarnings: update C warnings for GCC 15 + Adjust for C programs compiled by GCC 15. + This is merely changes to commentary; no changes to + the flags passed to GCC. + * build-aux/gcc-warning.spec: Add warnings introduced

[PATCH] manywarnings: update C warnings for GCC 14

-23 Paul Eggert + + manywarnings: update C warnings for GCC 14 + Adjust for C programs compiled by GCC 14. + (A C++ expert still needs to look at manywarnings-c++.m4.) + * build-aux/gcc-warning.spec: Add warnings introduced in GCC 13. + * m4/manywarnings.m4

[PATCH 3/4] manywarnings: update C warnings for GCC 13

(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 5246e88037..ff1f6abca3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,14 @@ 2023-04-23 Paul Eggert + manywarnings: update C warnings for GCC 13 + Adjust for C programs compiled by GCC 13. + (A C++ expert still needs

[PATCH] manywarnings: update C warnings for GCC 12

..6ed8a50735 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,13 @@ +2022-05-12 Paul Eggert + + manywarnings: update C warnings for GCC 12 + Adjust for C programs compiled by GCC 12. + (A C++ expert still needs to look at manywarnings-c++.m4.) + * build-aux/gcc-warning.spec: Add

Re: [PATCH] manywarnings: update for GCC 7

On 05/16/2017 10:41 AM, Bruno Haible wrote: Why not # define FALLTHROUGH ? Would that generate warnings about empty statements? Yes, that was the worry. I didn't actually observe the warnings, but I assume some compilers will generate them. Thanks for the sigpipe-tests fix.

Re: [PATCH] manywarnings: update for GCC 7

Log b/ChangeLog index ec82d08..9eedc53 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2017-05-16 Bruno Haible + + sigpipe tests: Fix file list. + * modules/sigpipe-tests (Files): Add tests/macros.h. + 2017-05-16 Paul Eggert manywarnings: update for GCC 7 @@ -9,

[PATCH] manywarnings: update for GCC 7

tests/test-mbrtowc.c | 2 +- tests/test-sigpipe.c | 4 +++- 12 files changed, 126 insertions(+), 25 deletions(-) diff --git a/ChangeLog b/ChangeLog index 2fa97a2..ec82d08 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,15 @@ +2017-05-16 Paul Eggert + + manywarnings

Re: [PATCH] manywarnings: update for GCC 6.1

On Tue, May 17, 2016 at 9:08 AM, Paul Eggert wrote: > * m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC): > Add GCC 6.1 options that apply to C. > * build-aux/gcc-warning.spec: Add GCC 6.1 options that > do not apply to C, are obsolescent, etc. Thanks!

[PATCH] manywarnings: update for GCC 6.1

| 14 +- 3 files changed, 42 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index a9c66e9..02a0f6f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2016-05-17 Paul Eggert + + manywarnings: update for GCC 6.1 + * m4/manywarnings.m4

[PATCH] manywarnings: update for GCC 4.8.0

ChangeLog | 8 m4/manywarnings.m4 | 6 ++ 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 171fa5d..c03bf8c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,13 @@ 2013-05-15 Paul Eggert + manywarnings: update for GCC

Re: manywarnings update

Simon Josefsson wrote: > I have pushed the patch below. For Libtasn1, the only new warning flag > I had to manually disable for that project was -Wsuggest-attribute=pure > because there were many hits and I didn't feel like adding many function > attributes. Unfortunately, several of the paramet

manywarnings update

I have pushed the patch below. For Libtasn1, the only new warning flag I had to manually disable for that project was -Wsuggest-attribute=pure because there were many hits and I didn't feel like adding many function attributes. Unfortunately, several of the parameters aren't documented in the man