public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105458] [12/13 Regression] ICE in set_relation, at value-relation.cc:609 since r12-4790-g4b3a325f07acebf4 Date: Tue, 17 May 2022 15:44:56 +0000 [thread overview] Message-ID: <bug-105458-4-2BMWxtSFhg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105458-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105458 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:6101a276c34b94f692206739d98aa7faf2e7b2ad commit r13-564-g6101a276c34b94f692206739d98aa7faf2e7b2ad Author: Andrew MacLeod <amacleod@redhat.com> Date: Mon May 16 21:39:30 2022 -0400 Check for equivalence after merging relations. When registering a relation, we need to merge with any existing relation before checking if it was an equivalence... otherwise it was not being handled properly. gcc/ PR tree-optimization/105458 * value-relation.cc (path_oracle::register_relation): Merge, then check for equivalence. gcc/testsuite/ * gcc.dg/pr105458.c: New.
next prev parent reply other threads:[~2022-05-17 15:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 3:25 [Bug tree-optimization/105458] New: [12/13 Regression] ICE in set_relation, at value-relation.cc:609 asolokha at gmx dot com 2022-05-03 6:52 ` [Bug tree-optimization/105458] " rguenth at gcc dot gnu.org 2022-05-03 8:44 ` [Bug tree-optimization/105458] [12/13 Regression] ICE in set_relation, at value-relation.cc:609 since r12-4790-g4b3a325f07acebf4 marxin at gcc dot gnu.org 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-17 15:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-18 14:13 ` cvs-commit at gcc dot gnu.org 2022-07-26 11:36 ` 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-105458-4-2BMWxtSFhg@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).