> > Otherwise > > I will add your testcase for this patch and commit this one. > > Statistically we almost never merge functions with different value > > ranges (three in testsuite, 0 during bootstrap, 1 during LTO bootstrap > > and probably few in LLVM build - there are 15 cases reported, but some > > are false positives caused by hash function conflicts). > > It is mostly the fnsplit functions, sure, because we don't really drop > the __builtin_unreachable checks before IPA and so the if (cond) > __builtin_unreachable (); style assertions or [[assume (cond)]]; still > result in ICF failures.
Actually on llvm they are not split functions, but functions where value ranges were determined by early VRP based on code optimized out by time we reach ipa-icf (the equal thingy from libstdc++ I wrote about in previous email) Honza
