https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117695
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, I suppose whatever dhry2reg is computing isn't used so it's fair to
eliminate the computation. I would not recommend to use -flto with
benchmarks as often constant passed parameters get known to the kernels
benchmarked and you end up benchmarking something else than intended.
Another possibility is to exclude the "driver" from LTO by not compiling
that TU with -flto.
This isn't a bug but a problem with the benchmark or the user.
