subject:"\[Bug c\/98217\] Prefer a warning for when VLAs declared on stack"

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread svoboda at cert dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 David Svoboda changed: What|Removed |Added CC||svoboda at cert dot org --- Comment #1 f

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread svoboda at cert dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #2 from David Svoboda --- I have also submitted a similar bug report to Clang, it is here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread msebor at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 Martin Sebor changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread svoboda at cert dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #4 from David Svoboda --- Martin: Thanks. It looks like -Wvla-larger-than=0 is (theoretically) a good way to catch VLA stack declarations. There is still the issue that GCC's -Wvla did not flag use of array[*]. To me that is lower-

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread svoboda at cert dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #5 from David Svoboda --- Oops, the Clang bug entry is really here: https://bugs.llvm.org/show_bug.cgi?id=48460

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-09 Thread richard-gccbugzilla at metafoo dot co.uk via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 Richard Smith changed: What|Removed |Added CC||richard-gccbugzilla@metafoo

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-13 Thread muecker at gwdg dot de via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 Martin Uecker changed: What|Removed |Added CC||muecker at gwdg dot de --- Comment #7 fr

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-13 Thread msebor at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 Martin Sebor changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment #8 f

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-14 Thread svoboda at cert dot org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #9 from David Svoboda --- The more I think about it, the more I want to see two -W warnings...one to flag VLA declarations on the stack, and another to see *any* use of VLAs, even if in something as harmless as a conformant array. The

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-14 Thread muecker at gwdg dot de via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #10 from Martin Uecker --- (for C++ compatibility, there is: -Wc++XX-compat ) So since Xmas is coming: - I would also like an option to allocate VLAs of unbounded size larger than X on the heap. - Better code generation for VLAs.

[Bug c/98217] Prefer a warning for when VLAs declared on stack

2020-12-15 Thread joseph at codesourcery dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217 --- Comment #11 from joseph at codesourcery dot com --- It would seem reasonable to have options both for the case of warning about all VLA declarations, and more specifically for the case of allocating a VLA on the stack. The diagnostics for