[Bug middle-end/323] optimized code gives strange floating point results
- To: debian-gcc@lists.debian.org
- Subject: [Bug middle-end/323] optimized code gives strange floating point results
- From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
- Date: Fri, 07 Feb 2020 18:22:49 +0000
- Message-id: <bug-323-5724-oG7ZNK1Ucj@http.gcc.gnu.org/bugzilla/>
- In-reply-to: <bug-323-5724@http.gcc.gnu.org/bugzilla/>
- References: <bug-323-5724@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
--- Comment #217 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Fri, 7 Feb 2020, vincent-gcc at vinc17 dot net wrote:
> According to https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html#bug_status
> the possible status are UNCONFIRMED, CONFIRMED and IN_PROGRESS. I think that
> the correct one is CONFIRMED.
That's generic Bugzilla documentation that's not relevant to the custom
GCC configuration of bug states, which is documented at
<https://gcc.gnu.org/bugs/management.html> (we also have NEW and ASSIGNED
not CONFIRMED and IN_PROGRESS). SUSPENDED is accurate for a bug that is
explicitly known to be hard and not being worked on, for reasons other
than waiting for further information from the submitter. It's completely
correct for this bug, which should be left as SUSPENDED unless someone
decides to work on it and so changes it to ASSIGNED with themselves as
assignee.
--
You are receiving this mail because:
You are on the CC list for the bug.
Reply to: