summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorAdam Nemet <anemet@apple.com>2016-08-26 15:58:34 +0000
committerAdam Nemet <anemet@apple.com>2016-08-26 15:58:34 +0000
commit4f155b6e9122d4a95d98cab04ac4a18a64e389d5 (patch)
treef84056ebd738f4f2c80a31b47414f85cb35b7959 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parentf7ba0891ce6369cee4245991824a73279ca31258 (diff)
downloadbcm5719-llvm-4f155b6e9122d4a95d98cab04ac4a18a64e389d5.tar.gz
bcm5719-llvm-4f155b6e9122d4a95d98cab04ac4a18a64e389d5.zip
[LoopUnroll] Use OptimizationRemarkEmitter directly not via the analysis pass
We can't mark ORE (a function pass) preserved as required by the loop passes because that is how we ensure that the required passes like LazyBFI are all available any time ORE is used. See the new comments in the patch. Instead we use it directly just like the inliner does in D22694. As expected there is some additional overhead after removing the caching provided by analysis passes. The worst case, I measured was LNT/CINT2006_ref/401.bzip2 which regresses by 12%. As before, this only affects -Rpass-with-hotness and not default compilation. llvm-svn: 279829
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud