aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/IR/Module.cpp
diff options
context:
space:
mode:
authorJay Foad <jay.foad@amd.com>2022-01-12 14:56:20 +0000
committerJay Foad <jay.foad@amd.com>2022-01-13 09:47:37 +0000
commit821dd3b0e5b7811857e0fd0d1e9fca5ae2546cb4 (patch)
tree45b56a76111d9dba9b35204f06b64b91efa0386a /llvm/lib/IR/Module.cpp
parent31009f0b5afb504fc1f30769c038e1b7be6ea45b (diff)
downloadllvm-821dd3b0e5b7811857e0fd0d1e9fca5ae2546cb4.zip
llvm-821dd3b0e5b7811857e0fd0d1e9fca5ae2546cb4.tar.gz
llvm-821dd3b0e5b7811857e0fd0d1e9fca5ae2546cb4.tar.bz2
[FileCheck] Allow literal '['s before "[[var...]]"
Change FileCheck to accept patterns like "[[[var...]]" and treat the excess open brackets at the start as literals. This makes the patterns for matching assembler output with literal brackets much cleaner. For example an AMDGPU pattern that used to be written like: buffer_store_dwordx2 v{{\[}}[[LO]]:[[HI]]{{\]}} can now be: buffer_store_dwordx2 v[[[LO]]:[[HI]]] (Even before this patch the final close bracket did not need to be wrapped in {{}}, but people tended to do it anyway for symmetry.) This does not introduce any ambiguity since "[[" was always followed by an identifier or '@' or '#', so "[[[" was always an error. I've included a few test updates in this patch just for illustration and testing. There are a couple of hundred tests that could be updated as a follow up, mostly in test/CodeGen/. Differential Revision: https://reviews.llvm.org/D117117 Change-Id: Ia6bc6f65cb69734821c911f54a43fe1c673bcca7
Diffstat (limited to 'llvm/lib/IR/Module.cpp')
0 files changed, 0 insertions, 0 deletions