summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/python-extensions.swig
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2015-11-10 16:48:53 +0000
committerSanjay Patel <spatel@rotateright.com>2015-11-10 16:48:53 +0000
commit766589efdce379bd905a126180fead66760acda7 (patch)
tree263e27585632cd11256314f909c4074800cf656d /lldb/scripts/Python/python-extensions.swig
parent8b05278b4ebbce338fbd5604340a64dab6c8d415 (diff)
downloadbcm5719-llvm-766589efdce379bd905a126180fead66760acda7.tar.gz
bcm5719-llvm-766589efdce379bd905a126180fead66760acda7.zip
add 'MustReduceDepth' as an objective/cost-metric for the MachineCombiner
This is one of the problems noted in PR25016: https://llvm.org/bugs/show_bug.cgi?id=25016 and: http://lists.llvm.org/pipermail/llvm-dev/2015-October/090998.html The spilling problem is independent and not addressed by this patch. The MachineCombiner was doing reassociations that don't improve or even worsen the critical path. This is caused by inclusion of the "slack" factor when calculating the critical path of the original code sequence. If we don't add that, then we have a more conservative cost comparison of the old code sequence vs. a new sequence. The more liberal calculation must be preserved, however, for the AArch64 MULADD patterns because benchmark regressions were observed without that. The two failing test cases now have identical asm that does what we want: a + b + c + d ---> (a + b) + (c + d) Differential Revision: http://reviews.llvm.org/D13417 llvm-svn: 252616
Diffstat (limited to 'lldb/scripts/Python/python-extensions.swig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud