Changes in check_attrs.ll.funcattrs.expected

6398903a - Extend the `uwtable` attribute with unwind table kind

Mon, 14 Feb 2022 13:41:34 +0000

Extend the `uwtable` attribute with unwind table kindWe have the `clang -cc1` command-line option `-funwind-tables=1|2` andthe codegen option `VALUE_CODEGENOPT(UnwindTables, 2, 0) ///< Unwindtables (1) or asynchronous unwind tables (2)`. However, this isencoded in LLVM IR by the presence or the absence of the `uwtable`attribute, i.e. we lose the information whether to generate want justsome unwind tables or asynchronous unwind tables.Asynchronous unwind tables take more space in the runtime image, I'destimate something like 80-90% more, as the difference is addingroughly the same number of CFI directives as for prologues, only a bitsimpler (e.g. `.cfi_offset reg, off` vs. `.cfi_restore reg`). Or evenmore, if you consider tail duplication of epilogue blocks.Asynchronous unwind tables could also restrict code generation tohaving only a finite number of frame pointer adjustments (an exampleof *not* having a finite number of `SP` adjustments is on AArch64 whenuntagging the stack (MTE) in some cases the compiler can modify `SP`in a loop).Having the CFI precise up to an instruction generally also means onecannot bundle together CFI instructions once the prologue is done,they need to be interspersed with ordinary instructions, which meansextra `DW_CFA_advance_loc` commands, further increasing the unwindtables size.That is to say, async unwind tables impose a non-negligible overhead,yet for the most common use cases (like C++ exceptions), they are noteven needed.This patch extends the `uwtable` attribute with an optionalvalue: - `uwtable` (default to `async`) - `uwtable(sync)`, synchronous unwind tables - `uwtable(async)`, asynchronous (instruction precise) unwind tablesReviewed By: MaskRayDifferential Revision: https://reviews.llvm.org/D114543 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

d19e5302 - [UpdateTestChecks][FIX] Expected output changed with Attributor

Tue, 01 Feb 2022 08:18:02 +0000

[UpdateTestChecks][FIX] Expected output changed with Attributor List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

40760060 - [test] Use -passes in lit tests for the UpdateTestChecks tool

Thu, 18 Nov 2021 15:51:19 +0000

[test] Use -passes in lit tests for the UpdateTestChecks toolThe UpdateTestChecks tool itself does not care about which passmanager that is used in the opt invocation. So the lit tests thatare verifying the behavior of the UpdateTestChecks tool is updatedto use the new-PM syntax (-passes=) when specifying the pass pipelinein the test cases that are used for verifying the UpdateTestCheckstool.Differential Revision: https://reviews.llvm.org/D114517 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

cd1bd6e5 - [Utils] Check for more global information in update_test_checks

Fri, 15 Jan 2021 03:13:23 +0000

[Utils] Check for more global information in update_test_checksThis allows to check for various globals (metadata/attributes/...) andalso resolves problems with globals (metadata/attributes/...) beingreused across different prefixes.Reviewed By: sstefan1Differential Revision: https://reviews.llvm.org/D94741 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

7128e647 - [UpdateTestChecks] include { in function signature check line

Fri, 28 Aug 2020 08:19:04 +0000

[UpdateTestChecks] include { in function signature check lineAfter D85099, if we have attribute group in the function signature that hasn'tbeen seen before, and later a callsite with the same attribute group, filecheck will evaluatethe first attribute group to for example '#0 {'. We now include { in the args_and_sig group to avoid this.Differential Revision: https://reviews.llvm.org/D86769 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

97ce7fd8 - [UpdateTestChecks] Match unnamed values like "@[0-9]+" and "![0-9]+"

Mon, 10 Aug 2020 18:59:07 +0000

[UpdateTestChecks] Match unnamed values like "@[0-9]+" and "![0-9]+"With this patch we will match most *uses* of "temporary" named things inthe IR via regular expressions, not their name at creation time. The new"values" we match are: - "unnamed" globals: `@[0-9]+` - debug metadata: `!dbg ![0-9]+` - loop metadata: `!loop ![0-9]+` - tbaa metadata: `!tbaa ![0-9]+` - range metadata: `!range ![0-9]+` - generic metadata: `metadata ![0-9]+` - attributes groups: `#[0-9]`We still don't match the declarations but that can be done later. Thispatch can introduce churn when existing check lines contain the oldhardcoded versions of the above "values". We can add a flag to opt-out,or opt-in, if necessary.Reviewed By: arichardson, MaskRayDifferential Revision: https://reviews.llvm.org/D85099 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

cf110506 - [Utils][Fix] remove unnecessary ; at the end

Sun, 19 Jul 2020 18:45:24 +0000

[Utils][Fix] remove unnecessary ; at the end List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected

937bad35 - [Utils] Check function attributes in update_test_checks

Sat, 11 Jul 2020 19:53:50 +0000

[Utils] Check function attributes in update_test_checksSummary:This introduces new flag to the update_test_checks andupdate_cc_test_checks that allows for function attributesto be checked in a check-line. If the flag is not set,the behavior should remain the same.Reviewers: jdoerfertSubscribers: arichardson, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D83629 List of files: /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_test_checks/Inputs/check_attrs.ll.funcattrs.expected