aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Analysis/CodeMetrics.cpp
diff options
context:
space:
mode:
authorRichard Smith <richard@metafoo.co.uk>2020-05-08 19:24:18 -0700
committerRichard Smith <richard@metafoo.co.uk>2020-05-08 19:32:00 -0700
commitc90e198107431f64b73686bdce31c293e3380ac7 (patch)
tree927aae2095e064266ba799a942dd3d928c4b231e /llvm/lib/Analysis/CodeMetrics.cpp
parent49b32d80416288b6eb8e26f76c40a8e32c20a361 (diff)
downloadllvm-c90e198107431f64b73686bdce31c293e3380ac7.zip
llvm-c90e198107431f64b73686bdce31c293e3380ac7.tar.gz
llvm-c90e198107431f64b73686bdce31c293e3380ac7.tar.bz2
Fix parsing of enum-base to follow C++11 rules.
Previously we implemented non-standard disambiguation rules to distinguish an enum-base from a bit-field but otherwise treated a : after an elaborated-enum-specifier as introducing an enum-base. That misparses various examples (anywhere an elaborated-type-specifier can appear followed by a colon, such as within a ternary operator or _Generic). We now implement the C++11 rules, with the old cases accepted as extensions where that seemed reasonable. These amount to: * an enum-base must always be accompanied by an enum definition (except in a standalone declaration of the form 'enum E : T;') * in a member-declaration, 'enum E :' always introduces an enum-base, never a bit-field * in a type-specifier (or similar context), 'enum E :' is not permitted; the colon means whatever else it would mean in that context. Fixed underlying types for enums are also permitted in Objective-C and under MS extensions, plus as a language extension in all other modes. The behavior in ObjC and MS extensions modes is unchanged (but the bit-field disambiguation is a bit better); remaining language modes follow the C++11 rules. Fixes PR45726, PR39979, PR19810, PR44941, and most of PR24297, plus C++ core issues 1514 and 1966.
Diffstat (limited to 'llvm/lib/Analysis/CodeMetrics.cpp')
0 files changed, 0 insertions, 0 deletions