The existing check run label "DEFAULT" may clash with
the label from switch "DEFAULT", so renaming it for clarity.
Details
- Reviewers
nikic - Commits
- rG608cf17b734b: [InstCombine][NFC] Rename check run label
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Note: I am aware the "DEFAULT" prefix is currently unused, but was not sure if the intention was for it to be used in the near future - so I am leaving it there for now.
The existing check run label "DEFAULT" may clash with
the label from switch "DEFAULT", so renaming it for clarity.
Not sure I understand the clash. The check-prefixes and the variable names shouldn't clash, right?
llvm/test/Transforms/InstCombine/unreachable-code.ll | ||
---|---|---|
146 | Part of this line contains a substring that could potentially be matched with the check run line "DEFAULT:". |
LGTM -- The described file check behavior seems very weird to me, but changing the prefix doesn't hurt either.
llvm/test/Transforms/InstCombine/unreachable-code.ll | ||
---|---|---|
146 | Is that intentional FileCheck behavior rather than a bug? It seems pretty odd to me that a check prefix would get matched inside a placeholder declaration of a different check prefix. |
llvm/test/Transforms/InstCombine/unreachable-code.ll | ||
---|---|---|
146 | Not sure - I was surprised to see this failing too. Maybe --match-full-lines would've avoided the failure, although I didn't check. |
Part of this line contains a substring that could potentially be matched with the check run line "DEFAULT:".