Don't iterate over SCC as we potentially modify it.
Verify module (and fix some broken ones).
Only run pass once and make sure that it's actually run.
Rename tests to just end in a number since I'm planning on adding a
bunch more which won't have good individual names. Instead, add comments
on the transformations that each test does.
Details
Details
- Reviewers
asbirlea rnk - Commits
- rG4c8c6368710e: [test] Cleanup some CGSCCPassManager tests
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/unittests/Analysis/CGSCCPassManagerTest.cpp | ||
---|---|---|
1809 | What do you think of this as an alternative code pattern for safe iteration of the nodes? for (... N : std::vector<LazyCallGraph::Node*>(C.begin(), C.end())) { ... } |
llvm/unittests/Analysis/CGSCCPassManagerTest.cpp | ||
---|---|---|
1809 | I initially attempted something like that, the issue is that C.begin()/end() return references and not pointers. |
llvm/unittests/Analysis/CGSCCPassManagerTest.cpp | ||
---|---|---|
1809 | Well, we could make it happen with mapped_iterator, or perhaps just encapsulating the vector construction into a function that returns the right std::vector. |
What do you think of this as an alternative code pattern for safe iteration of the nodes?