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 rtl-optimization/96264] [10 Regression] wrong code with -Os -fno-forward-propagate -fschedule-insns -fno-tree-ter Date: Wed, 31 Mar 2021 16:53:23 +0000 [thread overview] Message-ID: <bug-96264-4-mM2b7tkcKl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264 --- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:1b7c97f25b271f826958873bda4fafc4cfc5b60d commit r10-9644-g1b7c97f25b271f826958873bda4fafc4cfc5b60d Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Thu Feb 18 17:49:26 2021 -0500 [PR96264] LRA: Check output insn hard regs when updating available rematerialization after the insn Insn for rematerialization can contain a clobbered hard register. We can not move such insn through another insn setting up the same hard register. The patch adds such check. gcc/ChangeLog: PR rtl-optimization/96264 * lra-remat.c (reg_overlap_for_remat_p): Check also output insn hard regs. gcc/testsuite/ChangeLog: PR rtl-optimization/96264 * gcc.target/powerpc/pr96264.c: New.
next prev parent reply other threads:[~2021-03-31 16:53 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 11:00 [Bug rtl-optimization/96264] New: [10/11 " zsojka at seznam dot cz 2020-07-21 14:20 ` [Bug rtl-optimization/96264] " rguenth at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-07-23 10:56 ` marxin at gcc dot gnu.org 2020-10-12 12:44 ` rguenth at gcc dot gnu.org 2021-02-11 14:45 ` seurer at gcc dot gnu.org 2021-02-11 14:46 ` seurer at gcc dot gnu.org 2021-02-11 14:49 ` seurer at gcc dot gnu.org 2021-02-11 15:49 ` rguenth at gcc dot gnu.org 2021-02-11 16:00 ` jakub at gcc dot gnu.org 2021-02-11 16:19 ` seurer at gcc dot gnu.org 2021-02-11 18:43 ` jakub at gcc dot gnu.org 2021-02-11 19:01 ` jakub at gcc dot gnu.org 2021-02-17 15:47 ` vmakarov at gcc dot gnu.org 2021-02-18 22:51 ` cvs-commit at gcc dot gnu.org 2021-02-19 16:34 ` seurer at gcc dot gnu.org 2021-02-19 19:29 ` bergner at gcc dot gnu.org 2021-02-19 20:20 ` seurer at gcc dot gnu.org 2021-03-30 19:02 ` [Bug rtl-optimization/96264] [10 " bergner at gcc dot gnu.org 2021-03-30 21:33 ` vmakarov at gcc dot gnu.org 2021-03-31 7:16 ` rguenth at gcc dot gnu.org 2021-03-31 12:55 ` vmakarov at gcc dot gnu.org 2021-03-31 12:58 ` tnfchris at gcc dot gnu.org 2021-03-31 16:53 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-31 16:57 ` vmakarov at gcc dot gnu.org 2021-03-31 20:01 ` seurer 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-96264-4-mM2b7tkcKl@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).