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/115226] [15 regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_ssa failed Date: Mon, 27 May 2024 10:45:59 +0000 [thread overview] Message-ID: <bug-115226-4-YOQvjYnXZY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115226-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115226 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:f9fbb47987efc8b5261e4cc36613c928a8693493 commit r15-850-gf9fbb47987efc8b5261e4cc36613c928a8693493 Author: Richard Biener <rguenther@suse.de> Date: Mon May 27 09:40:19 2024 +0200 tree-optimization/115220 - fix store sinking virtual operand constraints The following makes sure the virtual operand updating when sinking stores works for the case we ignore paths to kills. The final sink location might not post-dominate the original stmt location which would require inserting of a virtual PHI which we do not support. PR tree-optimization/115220 PR tree-optimization/115226 * tree-ssa-sink.cc (statement_sink_location): When ignoring paths to kills when sinking stores make sure the final sink location is still post-dominated by the original one. Otherwise we'd need to insert a PHI node to merge virtual operands. * gcc.dg/torture/pr115220.c: New testcase. * gcc.dg/torture/pr115226.c: New testcase.
next prev parent reply other threads:[~2024-05-27 10:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-25 13:44 [Bug tree-optimization/115226] New: " zhendong.su at inf dot ethz.ch 2024-05-26 6:47 ` [Bug tree-optimization/115226] [15 regression] " pinskia at gcc dot gnu.org 2024-05-27 7:00 ` rguenth at gcc dot gnu.org 2024-05-27 8:49 ` rguenth at gcc dot gnu.org 2024-05-27 9:01 ` rguenth at gcc dot gnu.org 2024-05-27 10:21 ` jakub at gcc dot gnu.org 2024-05-27 10:45 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-27 10:46 ` rguenth at gcc dot gnu.org 2024-05-28 6:31 ` 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-115226-4-YOQvjYnXZY@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).