Happened earlier than I anticipated. :)
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/AMDGPU/AMDGPUSetWavePriority.cpp | ||
---|---|---|
150–152 | These potentially invalidate Info. |
llvm/lib/Target/AMDGPU/AMDGPUSetWavePriority.cpp | ||
---|---|---|
150–152 | Doesn't this imply it's reading uncomputed values for the successors? Don't those need to be computed for this to do something sensible? |
llvm/lib/Target/AMDGPU/AMDGPUSetWavePriority.cpp | ||
---|---|---|
150–152 | I understand where the edge to a successor is a back edge, we will examine its MBBInfo here before the main post_order(&MF) loop had a chance to compute it. Logic-wise that itself is not a problem because we ignore loops, but since such successors are new to MBBInfos, this invalidates Info. |
I still think the initial implementation with non-relocatable MBBInfos would work better here.
Thanks for reviewing.
llvm/lib/Target/AMDGPU/AMDGPUSetWavePriority.cpp | ||
---|---|---|
150–152 | That's something to be tried and seen. We don't know it yet. |
Move &Info down here to avoid 2 map lookups?