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 target/110313] [14 Regression] GCN Fiji reload ICE in 'process_alt_operands' Date: Wed, 28 Jun 2023 14:06:41 +0000 [thread overview] Message-ID: <bug-110313-4-wacJnXjs0z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110313-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110313 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Philipp Tomsich <ptomsich@gcc.gnu.org>: https://gcc.gnu.org/g:893883f2f8f56984209c6ed210ee992ff71a14b0 commit r14-2165-g893883f2f8f56984209c6ed210ee992ff71a14b0 Author: Manolis Tsamis <manolis.tsamis@vrull.eu> Date: Tue Jun 20 16:23:52 2023 +0200 cprop_hardreg: fix ORIGINAL_REGNO/REG_ATTRS/REG_POINTER handling Fixes: 6a2e8dcbbd4bab3 Propagation for the stack pointer in regcprop was enabled in 6a2e8dcbbd4bab3, but set ORIGINAL_REGNO/REG_ATTRS/REG_POINTER for stack_pointer_rtx which caused regression (e.g., PR 110313, PR 110308). This fix adds special handling for stack_pointer_rtx in the places where maybe_mode_change is called. This also adds an check in maybe_mode_change to return the stack pointer only when the requested mode matches the mode of stack_pointer_rtx. PR debug/110308 gcc/ChangeLog: * regcprop.cc (maybe_mode_change): Check stack_pointer_rtx mode. (maybe_copy_reg_attrs): New function. (find_oldest_value_reg): Use maybe_copy_reg_attrs. (copyprop_hardreg_forward_1): Ditto. gcc/testsuite/ChangeLog: * g++.dg/torture/pr110308.C: New test. Signed-off-by: Manolis Tsamis <manolis.tsamis@vrull.eu> Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
prev parent reply other threads:[~2023-06-28 14:06 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 15:59 [Bug target/110313] New: " tschwinge at gcc dot gnu.org 2023-06-20 8:11 ` [Bug target/110313] " rguenth at gcc dot gnu.org 2023-06-20 9:13 ` ams at gcc dot gnu.org 2023-06-20 9:21 ` tschwinge at gcc dot gnu.org 2023-06-20 9:41 ` ams at gcc dot gnu.org 2023-06-20 15:36 ` tschwinge at gcc dot gnu.org 2023-06-20 15:56 ` ams at gcc dot gnu.org 2023-06-20 20:57 ` burnus at gcc dot gnu.org 2023-06-20 21:48 ` burnus at gcc dot gnu.org 2023-06-20 22:55 ` burnus at gcc dot gnu.org 2023-06-21 6:49 ` manolis.tsamis at vrull dot eu 2023-06-21 7:25 ` tschwinge at gcc dot gnu.org 2023-06-21 8:45 ` burnus at gcc dot gnu.org 2023-06-28 14:06 ` cvs-commit at gcc dot gnu.org [this message]
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-110313-4-wacJnXjs0z@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).