public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106805] [13 Regression] Undue optimisation of floating-point comparisons
Date: Fri, 02 Dec 2022 12:48:15 +0000 [thread overview]
Message-ID: <bug-106805-4-ORGZhPheCC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106805-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106805
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 54004
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54004&action=edit
gcc13-pr106805.patch
Untested patch. I believe fold_relational_const does it right, in the match.pd
case we are doing it just for simple_comparison, so a subset of those, so
only ==/!= are quiet from those.
Unfortunately, the patch isn't enough. On 12 branch it is enough until
expansion but during expansion we just drop the comparisons for some reason,
and on 13 branch it is worse, frange kicks in and we have the PR107608
problems.
next prev parent reply other threads:[~2022-12-02 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106805-4@http.gcc.gnu.org/bugzilla/>
2022-11-30 19:30 ` pinskia at gcc dot gnu.org
2022-12-02 12:48 ` jakub at gcc dot gnu.org [this message]
2022-12-02 12:49 ` jakub at gcc dot gnu.org
2022-12-05 10:55 ` cvs-commit at gcc dot gnu.org
2022-12-20 14:55 ` rguenth at gcc dot gnu.org
2023-01-13 11:27 ` rguenth at gcc dot gnu.org
2023-01-13 11:28 ` rguenth at gcc dot gnu.org
2023-01-13 16:56 ` vincent-gcc at vinc17 dot net
2023-02-03 9:23 ` jakub at gcc dot gnu.org
2023-02-27 9:14 ` [Bug middle-end/106805] " rguenth at gcc dot gnu.org
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-106805-4-ORGZhPheCC@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).