aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2020-07-30 10:15:47 +0100
committerFlorian Hahn <flo@fhahn.com>2020-07-30 12:36:27 +0100
commite77624a3be942c7abba48942b3a8da3462070a3f (patch)
treea28c66f6ed71d2880eadc91ea35081c13bcbe9f7 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parentcc529285fd621c6f4f5de77c8de10ac0bb7ce190 (diff)
downloadllvm-e77624a3be942c7abba48942b3a8da3462070a3f.zip
llvm-e77624a3be942c7abba48942b3a8da3462070a3f.tar.gz
llvm-e77624a3be942c7abba48942b3a8da3462070a3f.tar.bz2
[IPConstProp] Remove and move tests to SCCP.
As far as I know, ipconstprop has not been used in years and ipsccp has been used instead. This has the potential for confusion and sometimes leads people to spend time finding & reporting bugs as well as updating it to work with the latest API changes. This patch moves the tests over to SCCP. There's one functional difference I am aware of: ipconstprop propagates for each call-site individually, so for functions that are called with different constant arguments it can sometimes produce better results than ipsccp (at much higher compile-time cost).But IPSCCP can be thought to do so as well for internal functions and as mentioned earlier, the pass seems unused in practice (and there are no plans on working towards enabling it anytime). Also discussed on llvm-dev: http://lists.llvm.org/pipermail/llvm-dev/2020-July/143773.html Reviewed By: jdoerfert Differential Revision: https://reviews.llvm.org/D84447
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions