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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217
Martin Sebor changed:
What|Removed |Added
Ever confirmed|0 |1
Severity|normal
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-
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217
Richard Smith changed:
What|Removed |Added
CC||richard-gccbugzilla@metafoo
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
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
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
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.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217
Martin Sebor changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98217
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|msebor at gcc dot
13 matches
Mail list logo