https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102008
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ok. Though, perhaps indeed trying to detect what phiopt optimizes and not sinking that case would be long term best, so that we don't do the ping pong.
