public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94083] inefficient soft-float x!=Inf code
Date: Wed, 28 Feb 2024 22:19:32 +0000	[thread overview]
Message-ID: <bug-94083-4-pZSleQYkzO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94083-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to Joseph S. Myers from comment #6)
> Contrary to what was claimed in bug 66462, I don't think there ever was a
> fixed patch. Note that in bug 66462 comment 19, "June" is June 2017 but
> "November" is November 2016 - the "November" one is the *older* one.

Ah, sorry, I misunderstood the situation. According to
<https://gcc.gnu.org/legacy-ml/gcc-patches/2017-08/msg01630.html> the earlier
version of that patch (the November 2016 one) was the one that did not have the
problems that caused it to be reverted. In response to review of that, big
changes were requested and in the process bugs were introduced. The buggy
version was then committed and reverted. The original version that did not have
those bugs could still be committed if a re-review, taking into account the
bugs that the rework introduced, would now see it as acceptable.

      parent reply	other threads:[~2024-02-28 22:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-94083-4@http.gcc.gnu.org/bugzilla/>
2020-11-07 21:22 ` wilson at gcc dot gnu.org
2021-08-16 21:40 ` pinskia at gcc dot gnu.org
2024-02-27 19:48 ` pinskia at gcc dot gnu.org
2024-02-27 19:49 ` pinskia at gcc dot gnu.org
2024-02-28  9:51 ` jakub at gcc dot gnu.org
2024-02-28 10:24 ` harald at gigawatt dot nl
2024-02-28 10:33 ` jakub at gcc dot gnu.org
2024-02-28 11:42 ` jsm28 at gcc dot gnu.org
2024-02-28 22:19 ` harald at gigawatt dot nl [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94083-4-pZSleQYkzO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).