[Bug middle-end/323] optimized code gives strange floating point results

egallager at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Fri Feb 7 04:04:00 GMT 2020


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=323

--- Comment #212 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Rich Felker from comment #211)
> If new reports are going to be marked as duplicates of this, then can it
> please be moved from SUSPENDED status to REOPENED? The situation is far
> worse than what seems to have been realized last this was worked on, as
> evidenced by pr 85957. These issues just came up again breaking real-world
> software in https://github.com/OSGeo/PROJ/issues/1906

Uh... I'm not seeing "REOPENED" on the menu for possible statuses? Maybe a bug
can only have the REOPENED status if it's actually been closed in the past, and
this might not have actually been closed before? I thought this had been closed
at one point, but it looks like I was wrong... Hold on, let me check the (very
long) history for this bug...


More information about the Gcc-bugs mailing list