summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/APFloat.cpp
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2013-08-28 05:21:45 +0000
committerHal Finkel <hfinkel@anl.gov>2013-08-28 05:21:45 +0000
commit108c46a7bf92342aa1661c36e4b85cd2b24d7f4e (patch)
tree10c19854f237c724736dab54bc76568e111fec6f /llvm/lib/Support/APFloat.cpp
parent7d0867f48c6adde6cb5c5df7f1c0068cf2f6a9f4 (diff)
downloadbcm5719-llvm-108c46a7bf92342aa1661c36e4b85cd2b24d7f4e.tar.gz
bcm5719-llvm-108c46a7bf92342aa1661c36e4b85cd2b24d7f4e.zip
Revert r189440 - Disable loop vectorizer unrolling when no unrolling requested
As Chandler pointed out, we should not be using -backend-option because this will cause crashes for users of the tooling interface, etc. A better way to fix this will be to provide the unrolling pass-manager flag to the loop vectorizer directly. Original commit message: Disable loop vectorizer unrolling when no unrolling requested In addition to the regular loop unrolling transformation, the loop vectorizer can also unroll loops. If no unrolling has specifically been requested (by -fno-unroll-loops), and the loop vectorizer will be used, then add the backend option to (also) prevent the loop vectorizer from unrolling loops. I confirmed with Nadav (off list) that disabling vectorizer loop unrolling when -fno-unroll-loops is provided is the desired behavior. llvm-svn: 189441
Diffstat (limited to 'llvm/lib/Support/APFloat.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud