It's quite common for ScalarEvolution to emit a "{{" sequence, which FileCheck
will interpret as the start of a regular expression. Escape such patterns so
that we can correctly match them in the auto-generated checks.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Are there tests for this tool? I ran into this issue with some downstream testing. I could mock-up a testcase but where does it go?
Comment Actions
I could mock-up a testcase but where does it go?
As you mentioned SCEV, you can add new/update test for SCEV. But I dont think this "step" is required.
Comment Actions
So, that leaves me with a question. What else needs to be done before getting this committed?
Comment Actions
You can attach a minimalist example with generated CHECK lines before/after this change in the summary. Logic in this script is very tricky and such examples in the git logs will be very helpful to a future poor soul hacking the source.