diff options
| author | Pete Cooper <peter_cooper@apple.com> | 2019-01-03 01:38:08 +0000 |
|---|---|---|
| committer | Pete Cooper <peter_cooper@apple.com> | 2019-01-03 01:38:08 +0000 |
| commit | 697281df42916d736cc23e74c2a2b2275786c43f (patch) | |
| tree | b9ee5c2c9551079578769dc8bf5a081b65cc8df5 /llvm/lib/Transforms/Hello | |
| parent | ddc62017ea18ea08afc6c4b1e5c57198f1222e36 (diff) | |
| download | bcm5719-llvm-697281df42916d736cc23e74c2a2b2275786c43f.tar.gz bcm5719-llvm-697281df42916d736cc23e74c2a2b2275786c43f.zip | |
Teach ObjCARC optimizer about equivalent PHIs when eliminating autoreleaseRV/retainRV pairs
OptimizeAutoreleaseRVCall skips optimizing llvm.objc.autoreleaseReturnValue if it
sees a user which is llvm.objc.retainAutoreleasedReturnValue, and if they have
equivalent arguments (either identical or equivalent PHIs). It then assumes that
ObjCARCOpt::OptimizeRetainRVCall will optimize the pair instead.
Trouble is, ObjCARCOpt::OptimizeRetainRVCall doesn't know about equivalent PHIs
so optimizes in a different way and we are left with an unoptimized llvm.objc.autoreleaseReturnValue.
This teaches ObjCARCOpt::OptimizeRetainRVCall to also understand PHI equivalence.
rdar://problem/47005143
Reviewed By: ahatanak
Differential Revision: https://reviews.llvm.org/D56235
llvm-svn: 350284
Diffstat (limited to 'llvm/lib/Transforms/Hello')
0 files changed, 0 insertions, 0 deletions
