public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108447] [13 Regression] glibc math/test-*-iseqsig failures
Date: Wed, 18 Jan 2023 22:21:29 +0000 [thread overview]
Message-ID: <bug-108447-4-8Pc5EDXQ8i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108447-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108447
--- Comment #6 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Jakub Jelinek from comment #4)
> I see fold_using_range::relation_fold_and_or
> which sees relation1 VREL_LE and relation2 VREL_GE and !is_and, and because
> of
> relation_union (relation1, relation2) == VREL_VARYING fold it to 1.
> But for floating point comparisons, LE | GE is not always true, it is true if
> neither operand is NAN, otherwise false.
right.. we're sorting out whether these relations should be created or not, and
if so, how to then verify the result of a union/intersection before committing
to it. That validate_relation routine was created for a reason that we are
trying to track down why we arent using it, and if this is an appropriate use,
or if we need something else.
next prev parent reply other threads:[~2023-01-18 22:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:37 [Bug tree-optimization/108447] New: " jakub at gcc dot gnu.org
2023-01-18 17:37 ` [Bug tree-optimization/108447] " jakub at gcc dot gnu.org
2023-01-18 17:54 ` jakub at gcc dot gnu.org
2023-01-18 18:04 ` jakub at gcc dot gnu.org
2023-01-18 18:54 ` amacleod at redhat dot com
2023-01-18 19:48 ` jakub at gcc dot gnu.org
2023-01-18 20:19 ` jakub at gcc dot gnu.org
2023-01-18 22:21 ` amacleod at redhat dot com [this message]
2023-01-18 22:26 ` amacleod at redhat dot com
2023-01-19 10:02 ` aldyh at gcc dot gnu.org
2023-01-19 10:05 ` aldyh at gcc dot gnu.org
2023-01-19 10:16 ` jakub at gcc dot gnu.org
2023-01-19 10:17 ` aldyh at gcc dot gnu.org
2023-01-19 10:29 ` jakub at gcc dot gnu.org
2023-01-19 10:43 ` rguenther at suse dot de
2023-01-19 11:39 ` aldyh at gcc dot gnu.org
2023-01-19 16:05 ` jakub at gcc dot gnu.org
2023-01-19 16:32 ` jakub at gcc dot gnu.org
2023-01-19 20:00 ` amacleod at redhat dot com
2023-01-19 20:14 ` amacleod at redhat dot com
2023-01-19 21:28 ` amacleod at redhat dot com
2023-01-19 22:27 ` cvs-commit at gcc dot gnu.org
2023-01-20 15:24 ` jakub at gcc dot gnu.org
2023-01-20 15:36 ` amacleod at redhat dot com
2023-01-20 16:07 ` amacleod at redhat dot com
2023-01-20 16:59 ` jakub at gcc dot gnu.org
2023-01-23 17:26 ` amacleod at redhat dot com
2023-01-27 14:38 ` cvs-commit at gcc dot gnu.org
2023-01-27 14:41 ` amacleod at redhat dot com
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-108447-4-8Pc5EDXQ8i@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).