We always need the Dominator and PostDominatorTree for use-after-scope.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Failed Tests (2):
LLVM :: CodeGen/AArch64/O0-pipeline.ll LLVM :: CodeGen/AArch64/O3-pipeline.ll
Comment Actions
LGTM
TBH I'm on the fence about whether poison-at-lifetime is an optimization vs "core functionality", but lets go with this change. The important part is not to run the analysis when the function does not have the attribute (that's what the *-pipeline tests check).
Comment Actions
I think there should be a very high bar for disabling functionality with user-visible effects as "optimizations" because it adds lots of potential for confusion. In fact, from the perspective of the resulting code, the non-UAS code is potentially more optimized than the UAS one.