https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110218
--- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> --- So what I think was happening was that we would sink past a bunch of conditionals that were never going to be true thinking that we were moving to a deeper control nest. So the idea was to use the frequency information to avoid movements that weren't likely to improve anything. I don't remember how I selected the param's value though. I've got no objection to adjusting how this works.
