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 tree-optimization/108447] [13 Regression] glibc math/test-*-iseqsig failures
Date: Wed, 18 Jan 2023 20:19:01 +0000	[thread overview]
Message-ID: <bug-108447-4-0I238vyHS8@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 #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm surprised by rr_union_table content.
// VREL_VARYING
  { VREL_VARYING, VREL_VARYING, VREL_VARYING, VREL_VARYING, VREL_VARYING,
    VREL_VARYING, VREL_VARYING, VREL_VARYING },
is obviously correct, sure, but:
// VREL_UNDEFINED
  { VREL_VARYING, VREL_LT, VREL_LE, VREL_GT, VREL_GE, VREL_UNDEFINED,
    VREL_EQ, VREL_NE },
is strange, VREL_VARYING union VREL_UNDEFINED be VREL_LT?
I would have expected
  { VREL_VARYING, VREL_UNDEFINED, VREL_LT, VREL_LE, VREL_GT, VREL_GE,
    VREL_EQ, VREL_NE },
instead.
I fear other entries are weird too (though rr_intersect_table entries look
reasonable from quick skimming).
That said, fixing that will not fix this issue.

  parent reply	other threads:[~2023-01-18 20:19 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 [this message]
2023-01-18 22:21 ` amacleod at redhat dot com
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-0I238vyHS8@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).