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/109491] [11 Regression] Segfault in tree-ssa-sccvn.cc:expressions_equal_p() Date: Mon, 17 Apr 2023 10:44:47 +0000 [thread overview] Message-ID: <bug-109491-4-4HTGmSwlSz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109491 --- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:bb400f9916beab1a650d59c73672ef48aaf71b11 commit r11-10629-gbb400f9916beab1a650d59c73672ef48aaf71b11 Author: Richard Biener <rguenther@suse.de> Date: Thu Apr 13 14:09:30 2023 +0200 tree-optimization/109491 - ICE in expressions_equal_p At some point I elided the NULL pointer check in expressions_equal_p because it shouldn't be necessary not realizing that for example TARGET_MEM_REF has optional operands we cannot substitute with something non-NULL with the same semantics. The following does the simple thing and restore the check removed in r11-4982. PR tree-optimization/109491 * tree-ssa-sccvn.c (expressions_equal_p): Restore the NULL operands test. (cherry picked from commit a37783de23c067d6a26374ff29c014e49604035c)
next prev parent reply other threads:[~2023-04-17 10:44 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 20:25 [Bug tree-optimization/109491] New: " pthaugen at gcc dot gnu.org 2023-04-12 20:26 ` [Bug tree-optimization/109491] [13 Regression] " pinskia at gcc dot gnu.org 2023-04-12 20:46 ` pthaugen at gcc dot gnu.org 2023-04-12 20:52 ` pinskia at gcc dot gnu.org 2023-04-12 20:54 ` pinskia at gcc dot gnu.org 2023-04-12 21:08 ` bergner at gcc dot gnu.org 2023-04-12 21:16 ` pthaugen at gcc dot gnu.org 2023-04-13 11:34 ` rguenth at gcc dot gnu.org 2023-04-13 11:35 ` rguenth at gcc dot gnu.org 2023-04-13 12:07 ` rguenth at gcc dot gnu.org 2023-04-13 12:17 ` rguenth at gcc dot gnu.org 2023-04-13 13:00 ` cvs-commit at gcc dot gnu.org 2023-04-13 13:01 ` [Bug tree-optimization/109491] [11/12 " rguenth at gcc dot gnu.org 2023-04-13 16:22 ` chip.kerchner at ibm dot com 2023-04-14 7:17 ` rguenth at gcc dot gnu.org 2023-04-14 12:24 ` chip.kerchner at ibm dot com 2023-04-14 12:45 ` rguenther at suse dot de 2023-04-14 13:15 ` rguenth at gcc dot gnu.org 2023-04-14 13:32 ` hubicka at gcc dot gnu.org 2023-04-17 9:14 ` cvs-commit at gcc dot gnu.org 2023-04-17 10:44 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-17 10:46 ` [Bug tree-optimization/109491] [11 " 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-109491-4-4HTGmSwlSz@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).