diff options
author | Michael Gottesman <mgottesman@apple.com> | 2013-04-24 22:18:18 +0000 |
---|---|---|
committer | Michael Gottesman <mgottesman@apple.com> | 2013-04-24 22:18:18 +0000 |
commit | 3f4613310deac06c5a43c6ff76e7f9ab1e93503c (patch) | |
tree | f47e912fc4678d4a09e95b7df9ce1d1e16f5a412 /lib/ExecutionEngine/MCJIT/SectionMemoryManager.cpp | |
parent | 0eb5e45e4bd0099187009ef43aa63d2cb861560a (diff) | |
download | external_llvm-3f4613310deac06c5a43c6ff76e7f9ab1e93503c.zip external_llvm-3f4613310deac06c5a43c6ff76e7f9ab1e93503c.tar.gz external_llvm-3f4613310deac06c5a43c6ff76e7f9ab1e93503c.tar.bz2 |
[objc-arc] Added ImpreciseAutoreleaseSet to track autorelease calls that were once autoreleaseRV instructions.
Due to the semantics of ARC, we must be extremely conservative with autorelease
calls inserted by the frontend since ARC gaurantees that said object will be in
the autorelease pool after that point, an optimization invariant that the
optimizer must respect.
On the other hand, we are allowed significantly more flexibility with
autoreleaseRV instructions.
Often times though this flexibility is disrupted by early transformations which
transform objc_autoreleaseRV => objc_autorelease if said instruction is no
longer being used as part of an RV pair (generally due to inlining). Since we
can not tell the difference in between an autorelease put into place by the
frontend and one created through said ``strength reduction'' we can not perform
these optimizations.
The addition of this set gets around said issues by allowing us to differentiate
in between said two cases.
rdar://problem/13697741.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180222 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/ExecutionEngine/MCJIT/SectionMemoryManager.cpp')
0 files changed, 0 insertions, 0 deletions