diff options
| author | Richard Smith <richard@metafoo.co.uk> | 2020-10-15 19:32:15 -0700 |
|---|---|---|
| committer | Richard Smith <richard@metafoo.co.uk> | 2020-10-16 14:34:35 -0700 |
| commit | 552c6c2328723a248c2b4d2765f75d49129dff20 (patch) | |
| tree | c1583c5245e03d4aad54ecde9463158585a3b8a1 /llvm/lib/Object/TapiFile.cpp | |
| parent | 109113015ebeeceec862fc53a678b3619a879ce4 (diff) | |
| download | llvm-552c6c2328723a248c2b4d2765f75d49129dff20.zip llvm-552c6c2328723a248c2b4d2765f75d49129dff20.tar.gz llvm-552c6c2328723a248c2b4d2765f75d49129dff20.tar.bz2 | |
PR44406: Follow behavior of array bound constant folding in more recent versions of GCC.
Old GCC used to aggressively fold VLAs to constant-bound arrays at block
scope in GNU mode. That's non-conforming, and more modern versions of
GCC only do this at file scope. Update Clang to do the same.
Also promote the warning for this from off-by-default to on-by-default
in all cases; more recent versions of GCC likewise warn on this by
default.
This is still slightly more permissive than GCC, as pointed out in
PR44406, as we still fold VLAs to constant arrays in structs, but that
seems justifiable given that we don't support VLA-in-struct (and don't
intend to ever support it), but GCC does.
Differential Revision: https://reviews.llvm.org/D89523
Diffstat (limited to 'llvm/lib/Object/TapiFile.cpp')
0 files changed, 0 insertions, 0 deletions