public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] [PR103302] skip multi-part clobber during lra for complex parts too Date: Wed, 15 Dec 2021 06:06:04 +0000 (GMT) [thread overview] Message-ID: <20211215060604.AFF243858410@sourceware.org> (raw) https://gcc.gnu.org/g:5b5e92ea5eb9f4ced3908499519dada053f62f6c commit 5b5e92ea5eb9f4ced3908499519dada053f62f6c Author: Alexandre Oliva <oliva@adacore.com> Date: Wed Dec 15 03:00:57 2021 -0300 [PR103302] skip multi-part clobber during lra for complex parts too As with the earlier patch, avoid emitting clobbers that we used to avoid during reload also during LRA, now when moving complex multi-part values. We don't have a testcase for this one. for gcc/ChangeLog PR target/103302 * expr.c (emit_move_complex_parts): Skip clobbers during lra. Diff: --- gcc/expr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/expr.c b/gcc/expr.c index 0365625e7b8..30d1735ec29 100644 --- a/gcc/expr.c +++ b/gcc/expr.c @@ -3736,7 +3736,7 @@ emit_move_complex_parts (rtx x, rtx y) /* Show the output dies here. This is necessary for SUBREGs of pseudos since we cannot track their lifetimes correctly; hard regs shouldn't appear here except as return values. */ - if (!reload_completed && !reload_in_progress + if (!reload_completed && !reload_in_progress && !lra_in_progress && REG_P (x) && !reg_overlap_mentioned_p (x, y)) emit_clobber (x);
reply other threads:[~2021-12-15 6:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211215060604.AFF243858410@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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).