Instances of the AssumptionCache are per function, so we can't re-use
the same AssumptionCache instance when recursing in the CallAnalyzer to
analyze a different function. Instead we have to pass the
AssumptionCacheTracker to the CallAnalyzer so it can get the right
AssumptionCache on demand.
Details
Details
- Reviewers
chandlerc hfinkel - Commits
- rG2f356a13181d: Merging r228957: --------------------------------------------------------------…
rG6f972a13f6e5: Fix a crash in the assumption cache when inlining indirect function calls
rL228957: Fix a crash in the assumption cache when inlining indirect function calls
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Not sure if this still qualifies for 3.6 (I guess it's not strictly a regression since llvm.assume is new?), but it'd be nice if it would as we hit this bug with rustc when using llvm.assume.
Comment Actions
Yes, this is obviously correct. Thanks for the fix!
Also, yes, this should go into 3.6.