aboutsummaryrefslogtreecommitdiffstats
path: root/unittests/VMCore
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2012-04-16 13:49:17 +0000
committerChandler Carruth <chandlerc@gmail.com>2012-04-16 13:49:17 +0000
commit9e67db4af13abb967cae5858502207a43d26bf84 (patch)
treebf6e90af917516e3f1e962532b04f4f77fe8a154 /unittests/VMCore
parent0de089a4d0db7e47ac8a5d8bd087c196231c7572 (diff)
downloadexternal_llvm-9e67db4af13abb967cae5858502207a43d26bf84.zip
external_llvm-9e67db4af13abb967cae5858502207a43d26bf84.tar.gz
external_llvm-9e67db4af13abb967cae5858502207a43d26bf84.tar.bz2
Flip the new block-placement pass to be on by default.
This is mostly to test the waters. I'd like to get results from FNT build bots and other bots running on non-x86 platforms. This feature has been pretty heavily tested over the last few months by me, and it fixes several of the execution time regressions caused by the inlining work by preventing inlining decisions from radically impacting block layout. I've seen very large improvements in yacr2 and ackermann benchmarks, along with the expected noise across all of the benchmark suite whenever code layout changes. I've analyzed all of the regressions and fixed them, or found them to be impossible to fix. See my email to llvmdev for more details. I'd like for this to be in 3.1 as it complements the inliner changes, but if any failures are showing up or anyone has concerns, it is just a flag flip and so can be easily turned off. I'm switching it on tonight to try and get at least one run through various folks' performance suites in case SPEC or something else has serious issues with it. I'll watch bots and revert if anything shows up. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154816 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'unittests/VMCore')
0 files changed, 0 insertions, 0 deletions