GlobalsAA is only created at the beginning of the inliner pipeline. If
an AAManager is cached from previous passes, it won't get rebuilt to
include the newly created GlobalsAA.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Event Timeline
Comment Actions
don't mess with second GlobalsAA yet, that should be separated out since it's causing extra invalidation
Comment Actions
I decided to separate the change to rebuild GlobalsAA in the optimization pipeline since that was causing extra loop analysis invalidation