[Bug c/98541] warning with -Wnonnull for array parameter with bound > 0

2023-11-04 Thread uecker at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 uecker at gcc dot gnu.org changed: What|Removed |Added Known to fail||11.0 Resolution|---

[Bug c/98541] warning with -Wnonnull for array parameter with bound > 0

2023-11-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 --- Comment #4 from CVS Commits --- The master branch has been updated by Martin Uecker : https://gcc.gnu.org/g:6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b commit r14-5115-g6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b Author: Martin Uecker Date: Th

[Bug c/98541] warning with -Wnonnull for array parameter with bound > 0

2021-01-06 Thread muecker at gwdg dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 --- Comment #3 from Martin Uecker --- Having to set the length to 0 for NULL pointers is problematic also because zero-sized array types are now allowed in ISO C. On the other hand, an optional warning that warns for all parameters declared as

[Bug c/98541] warning with -Wnonnull for array parameter with bound > 0

2021-01-06 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 --- Comment #2 from Martin Sebor --- (In reply to Martin Sebor from comment #1) > and necessary to prevent this use case. I mean: ...to prevent invalidating it.

[Bug c/98541] warning with -Wnonnull for array parameter with bound > 0

2021-01-06 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0