VirtRegAuxInfo is an extensibility point, so the register allocator's
decision on which implementation to use should be communicated to the
other users - namely, LiveRangeEdit.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/CodeGen/RegAllocPBQP.cpp | ||
---|---|---|
806–809 | Tests passed fine, however, I'd prefer decoupling that fix from this change: should there be a regression in the field for the users of PBQP, it'd be revertible without affecting this change. | |
llvm/lib/CodeGen/SplitKit.h | ||
456–457 | They aren't public though. We can change the API, but I think that's a separate patch, wdyt? Also, it'd be debatable if that doesn't couple SplitEditor to the fact that VRAI has such members. But we can discuss that there. |
Did you see any problem by using PBQP VRAI?