[llvm-bugs] [Bug 46634] New: Filecheck {{$}} doesn't delimit DAG range as expected
via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Jul 8 04:11:08 PDT 2020
https://bugs.llvm.org/show_bug.cgi?id=46634
Bug ID: 46634
Summary: Filecheck {{$}} doesn't delimit DAG range as expected
Product: Test Suite
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: lit
Assignee: unassignedbugs at nondot.org
Reporter: paul_robinson at playstation.sony.com
CC: daniel at zuster.org, llvm-bugs at lists.llvm.org
Re http://lists.llvm.org/pipermail/llvm-dev/2020-July/143168.html
trying to match the two metadata tags in this line, in either order:
%r1 = add %r2, %r3 !some-metadata !1, !some-other-metadata !2
I had thought that using this would work:
CHECK: %r1 = add %r2, %r3
CHECK-DAG: !some-metadata
CHECK-DAG: !some-other-metadata
CHECK: {{$}}
That is, I expected the {{$}} to constrain the DAG range to the
same line that matched the "add" instruction. But it doesn't.
The above checks will happily match this:
%r1 = add %r2, %r3 !some-metadata
foobar
!some-other-metadata
and `--dump-input=always -v` shows the {{$}} matching after the
second DAG, regardless of how many lines away that is.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200708/a144859f/attachment.html>
More information about the llvm-bugs
mailing list