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

[egallager at gcc dot gnu.org]

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

--- Comment #213 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #212)
> (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...

OK, never mind, it looks like this bug has actually been closed before like I
thought originally; whether or not a bug can have its status changed to
REOPENED or not must depend on its current status, rather than any past status
it might have had... So, I guess I can either close it temporarily and then
immediately reopen it, or give it some other status. Which would you prefer?