public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/90275] [8/9 Regression] ICE: in insert_regs, at cse.c:1128 with -O2 -fno-dce -fno-tree-dce Date: Fri, 13 Mar 2020 09:11:15 +0000 [thread overview] Message-ID: <bug-90275-4-0FzFBGS1lI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90275-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90275 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #13 from Martin Liška <marxin at gcc dot gnu.org> --- commit r10-7149-g4aded535ea6ad7c362ab62d99af70e53c186d582 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Thu Mar 12 16:09:27 2020 -0600 Remove no-op register to register copies in CSE just like we remove no-op memory to memory copies. PR rtl-optimization/90275 * cse.c (cse_insn): Delete no-op register moves too. PR rtl-optimization/90275 * gcc.c-torture/compile/pr90275.c: New test.
next prev parent reply other threads:[~2020-03-13 9:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90275-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 22:14 ` law at redhat dot com 2020-03-13 9:11 ` marxin at gcc dot gnu.org [this message] 2020-03-18 22:08 ` cvs-commit at gcc dot gnu.org 2020-03-23 23:59 ` cvs-commit at gcc dot gnu.org 2020-03-25 20:13 ` cvs-commit at gcc dot gnu.org 2020-03-25 20:33 ` cvs-commit at gcc dot gnu.org 2020-04-02 20:43 ` dcb314 at hotmail dot com 2020-04-03 7:18 ` [Bug rtl-optimization/90275] [8/9/10 " marxin at gcc dot gnu.org 2020-04-06 20:57 ` law at redhat dot com 2020-04-06 22:52 ` law at redhat dot com 2020-04-17 21:41 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:32 ` [Bug rtl-optimization/90275] [8/9 " rguenth at gcc dot gnu.org 2021-05-14 9:51 ` [Bug rtl-optimization/90275] [9 " jakub at gcc dot gnu.org 2021-06-01 8:14 ` rguenth at gcc dot gnu.org 2021-09-28 14:50 ` dcb314 at hotmail dot com 2022-05-27 8:32 ` 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-90275-4-0FzFBGS1lI@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).