https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121026
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2025-07-11
Ever confirmed|0 |1
CC| |ppalka at gcc dot gnu.org
--- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> ---
confirmed
(In reply to Jonathan Wakely from comment #1)
> The optimizations are useful for -O0 where the loop won't get optimized
> away, but do we care? If the optimizations are incorrect for constant
> evaluation and have subtleties with what they're allowed to do (e.g. we must
> use ranges::iter_move not std::move) then it would be simpler to just remove
> them all.
Makes sense for GCC 16, but I guess on release branches we would want to fix
the optimizations instead of removing them.
