https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94440
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
BTW, given that -fexcess-precision= option is marked Optimization, I'd say this
has been a problem even before that commit and one could construct a testcase
where it triggers.
Like one function with __attribute__((optimize ("excess-precision=standard")))
and another one with __attribute__((optimize ("excess-precision=fast"))).
Though, target-globals.[ch] seems to have some (limited?) support also for
optimization_current_node, but it probably isn't invoked on changes to just
optimize attribute and no target attributes changes and not sure if it deals
correctly with target and optimize attribute changes etc. What a mess.
