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/109274] [13 Regression] ice in in_chain_p, at gimple-range-gori.cc:119 starting with r13-6787-g0963cb5fde158cce986 Date: Mon, 27 Mar 2023 08:49:49 +0000 [thread overview] Message-ID: <bug-109274-4-XseBodH095@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109274-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109274 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- As I said on gcc-patches, both my above patch and your patch cause FAIL: gcc.dg/tree-ssa/vrp-float-3a.c scan-tree-dump-not evrp "link_error" FAIL: gcc.dg/tree-ssa/vrp-float-4a.c scan-tree-dump-not evrp "link_error" regressions. The following patch fixes the 2 new tests and doesn't regress the above ones, but I haven't actually analyzed why the vrp-float-?a.c tests failed. --- gcc/gimple-range-gori.cc.jj 2023-03-24 17:27:30.788929236 +0100 +++ gcc/gimple-range-gori.cc 2023-03-27 10:40:53.350453280 +0200 @@ -658,7 +658,7 @@ gori_compute::compute_operand_range (vra // the result. if (lhs.varying_p ()) { - if (!vrel_ptr) + if (!vrel_ptr || vrel_ptr->kind () == VREL_VARYING) return false; // If there is a relation (ie: x != y) , it can only be relevant if // a) both elements are in the defchain
next prev parent reply other threads:[~2023-03-27 8:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 12:23 [Bug c++/109274] New: ice in in_chain_p, at gimple-range-gori.cc:119 dcb314 at hotmail dot com 2023-03-24 12:30 ` [Bug tree-optimization/109274] [13 Regression] ice in in_chain_p, at gimple-range-gori.cc:119 starting with r13-6787 jakub at gcc dot gnu.org 2023-03-24 12:48 ` [Bug tree-optimization/109274] [13 Regression] ice in in_chain_p, at gimple-range-gori.cc:119 starting with r13-6787-g0963cb5fde158cce986 rguenth at gcc dot gnu.org 2023-03-24 13:33 ` jakub at gcc dot gnu.org 2023-03-24 14:27 ` jakub at gcc dot gnu.org 2023-03-24 14:28 ` jakub at gcc dot gnu.org 2023-03-24 15:02 ` amacleod at redhat dot com 2023-03-24 15:10 ` jakub at gcc dot gnu.org 2023-03-27 7:46 ` slyfox at gcc dot gnu.org 2023-03-27 8:11 ` marxin at gcc dot gnu.org 2023-03-27 8:49 ` jakub at gcc dot gnu.org [this message] 2023-03-27 14:10 ` amacleod at redhat dot com 2023-03-28 3:05 ` amacleod at redhat dot com 2023-03-28 13:34 ` cvs-commit at gcc dot gnu.org 2023-03-28 13:35 ` amacleod at redhat dot com 2023-03-29 1:42 ` sam at gentoo dot 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-109274-4-XseBodH095@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: linkBe 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).