When one of GEP operands is a trivial PHI, it's possible that we do RAUW leaving asserting value handle in the map.
This causes assertion in build with enabled assertions and UB in splitLargeGEPOffsets when assertions are disabled.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
LGTM with one nit.
test/CodeGen/AArch64/cgp-trivial-phi-node.ll | ||
---|---|---|
3 ↗ | (On Diff #189875) | Don't need REQUIRES: asserts; presumably the test should still behave the same way even without assertions. :) |