As far as I know, ipconstprop has not been used in years and ipsccp has
been used instead for years. 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.
If there are people actively using it, I would love to hear.
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).