Changes in alignas_maybe_odr_cleanup.cpp

f46c41fe - [SystemZ][z/OS] fix lit test related to alignment

Tue, 23 Mar 2021 17:09:05 +0000

[SystemZ][z/OS] fix lit test related to alignmentThis patch is to fix lit test case failure relate to alignment, on z/OS, maximum alignment value for 64 bit mode is 16 and also fixed clang/test/Layout/itanium-union-bitfield.cpp, attribute ((aligned(4))) is needed for bit-field member in Union for z/OS because single bit-field has one byte alignment, this will make sure size and alignment will be correct value on z/OS.Differential Revision: https://reviews.llvm.org/D98793 List of files: /llvm-project-15.0.7/clang/test/AST/alignas_maybe_odr_cleanup.cpp

f63e3ea5 - [clang] Rework how and when APValues are dumped

Mon, 06 Jul 2020 20:50:23 +0000

[clang] Rework how and when APValues are dumpedCurrently APValues are dumped as a single string. This becomes quicklycompletely unreadable since APValue is a tree-like structure. Even a simpleexample is not pretty: struct S { int arr[4]; float f; }; constexpr S s = { .arr = {1,2}, .f = 3.1415f }; // Struct fields: Array: Int: 1, Int: 2, 2 x Int: 0, Float: 3.141500e+00With this patch this becomes: -Struct |-field: Array size=4 | |-elements: Int 1, Int 2 | `-filler: 2 x Int 0 `-field: Float 3.141500e+00Additionally APValues are currently only dumped as part of visiting aConstantExpr. This patch also dump the value of the initializer of constexprvariable declarations: constexpr int foo(int a, int b) { return a + b - 42; } constexpr int a = 1, b = 2; constexpr int c = foo(a, b) > 0 ? foo(a, b) : foo(b, a); // VarDecl 0x62100008aec8 col:17 c 'const int' constexpr cinit // |-value: Int -39 // `-ConditionalOperator 0x62100008b4d0 'int' // Do the above by moving the dump functions to TextNodeDumper which already hasthe machinery to display trees. The cases APValue::LValue, APValue::MemberPointerand APValue::AddrLabelDiff are left as they were before (unimplemented).We try to display multiple elements on the same line if they are considered tobe "simple". This is to avoid wasting large amounts of vertical space in anexample like: constexpr int arr[8] = {0,1,2,3,4,5,6,7}; // VarDecl 0x62100008bb78 col:17 arr 'int const[8]' constexpr cinit // |-value: Array size=8 // | |-elements: Int 0, Int 1, Int 2, Int 3 // | `-elements: Int 4, Int 5, Int 6, Int 7Differential Revision: https://reviews.llvm.org/D83183Reviewed By: aaron.ballman List of files: /llvm-project-15.0.7/clang/test/AST/alignas_maybe_odr_cleanup.cpp

ecbf2f5f - [clang][test][NFC] Also test for serialization in AST dump tests, part 2/n.

Sun, 21 Jun 2020 12:35:15 +0000

[clang][test][NFC] Also test for serialization in AST dump tests, part 2/n.The outputs between the direct ast-dump test and the ast-dump test afterdeserialization should match modulo a few differences.For hand-written tests, strip the ""s andthe "imported"s with sed.For tests generated with "make-ast-dump-check.sh", regenerate theoutput.Part 2/n. List of files: /llvm-project-15.0.7/clang/test/AST/alignas_maybe_odr_cleanup.cpp

2f7269b6 - Fix compiler crash when an expression parsed in the tentative parsing and must be claimed in the another evaluation context.

Fri, 29 May 2020 21:56:07 +0000

Fix compiler crash when an expression parsed in the tentative parsing and must be claimed in the another evaluation context.Summary:Clang crashes when trying to finish function body. MaybeODRUseExprs isnot empty because of const static data member parsed in outer evaluationcontext, upon call for isTypeIdInParens() function. It buildsannot_primary_expr, later parsed in ParseConstantExpression() ininner constant expression evaluation context.Reviewers: rjmccall, rsmithSubscribers: cfe-commitsTags: #clangDifferential Revision: https://reviews.llvm.org/D80925 List of files: /llvm-project-15.0.7/clang/test/AST/alignas_maybe_odr_cleanup.cpp