https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102554
John S <jschoen4 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|12.0 |
--- Comment #3 from John S <jschoen4 at gmail dot com> ---
(In reply to Martin Liška from comment #2)
> (In reply to Richard Biener from comment #1)
> > I suspect that the optimize() attribute resets the param value to its
> > default.
>
> Yes, it's fixed on master with g:r12-4038-g6de9f0c13b27c343.
>
> >
> > Martin - can you investigate / bisect?
>
> Sure, it started with r10-4944-g1e83bd7003e03160.
>
> I tend closing that as fixed, what do you think Richi?
I can confirm I am seeing g:r12-4038-g6de9f0c13b27c343 resolve the issue.
Is it possible to get this applied into the upcoming 10.4, 11.3 releases? It's
making upgrading to 10.x / 11.x versions challenging in certain latency
sensitive production environments.
