Because the MachineFunctionSplitter pass isn't initialized in
CodeGen.cpp, running LLC with --run-pass machine-function-splitter
doesn't work. Adding it to the initializeCodeGen makes the function
splitting directly testable with .mir tests.
Details
Details
- Reviewers
- None
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
60,030 ms | x64 debian > MLIR.Examples/standalone::test.toy |
Event Timeline
Comment Actions
Is there a specific reason to test MFS (on ARM) with MIR instead of .ll inputs? Only ~11% of the tests in test/CodeGen/AArch64 are in MIR, the rest are bitcode files. IMO bitcode is much easier to read, maintain and we can reuse most (all?) of the existing tests we have in machine-function-splitter.ll. So my preference would be to use bitcode unless there is a fundamental reason which blocks us from testing with bitcode.
Comment Actions
In a different review, I was asked to make MIR tests so that they only targeted a single pass. That doesn't seem necessary here, so I'll use bitcode tests instead. Dropping this revision and updating its dependents.