This improves consistency in the trace files as other entries are demangled too.
Fixes #45901.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Time | Test | |
---|---|---|
60,030 ms | x64 debian > MLIR.Examples/standalone::test.toy |
Event Timeline
Is it possible to test this?
llvm/lib/IR/LegacyPassManager.cpp | ||
---|---|---|
1412 | Please use a named capture list instead of [&}. |
I don't know, are there any tests for all the other scopes?
There is a generic test for the functionality.
llvm/lib/IR/LegacyPassManager.cpp | ||
---|---|---|
1412 | Ok. Just followed the pattern used by other call sites like https://github.com/llvm/llvm-project/blob/781b491bba9d798e53f7784dced3c2be77c81dd4/clang/lib/CodeGen/CodeGenModule.cpp#L3570 |
I don't know if there are tests. In any case, it's good to add one for this change, no? :)
Is the mode change on check-time-trace-sections.py intended? I did a count of python files under llvm-project and < 10% are 755. I'm not saying it is better one way or the other; I'm just ensuring it is intentional.
Well last time I checked it this code was still in use. When is it going to be deleted?
Also the test has value to ensure the new pass manager emits these entries as before.
This review may be stuck/dead, consider abandoning if no longer relevant.
Removing myself as reviewer in attempt to clean dashboard.
I can only refer to my last comment, even in latest trunk that code is still active for the codegen passes.
But meanwhile I found the corresponding new code.
Please use a named capture list instead of [&}.