public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/91804] [10 regression] r265398 breaks gcc.target/powerpc/vec-rlmi-rlnm.c Date: Wed, 01 Apr 2020 18:11:00 +0000 [thread overview] Message-ID: <bug-91804-4-jscMwL4R5V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91804 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW CC| |bergner at gcc dot gnu.org --- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> --- This extra move is created by IRA: Examining insn 22, def for 133 all ok and transp Creating newreg=134 from oldreg=133 rescanning insn with uid = 22. scanning new insn with uid = 25. New r134: setting preferred ALTIVEC_REGS, alternative VSX_REGS Why?! It was (insn 22 11 20 2 (set (reg:V16QI 133) (vec_duplicate:V16QI (const_int 8 [0x8]))) "vec-rlmi-rlnm.c":45:10 1204 {xxspltib_v16qi} (nil)) and it is used only in (insn 23 19 9 2 (set (reg:V2DI 127) (unspec:V2DI [ (reg:V16QI 133) ] UNSPEC_VSX_SIGN_EXTEND)) "vec-rlmi-rlnm.c":45:10 1533 {vsx_sign_extend_qi_v2di} (expr_list:REG_DEAD (reg:V16QI 133) (expr_list:REG_EQUAL (const_vector:V2DI [ (const_int 8 [0x8]) repeated x2 ]) (nil)))) so copying it to another reg cannot help anything here? Peter, can you take a look?
next parent reply other threads:[~2020-04-01 18:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91804-4@http.gcc.gnu.org/bugzilla/> 2020-04-01 18:11 ` segher at gcc dot gnu.org [this message] 2020-04-01 19:49 ` bergner at gcc dot gnu.org 2020-04-08 23:03 ` wschmidt at gcc dot gnu.org 2020-05-07 11:56 ` [Bug target/91804] [10/11 " jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:38 ` [Bug target/91804] [10/11/12/13 " jakub at gcc dot gnu.org 2023-06-20 9:04 ` [Bug target/91804] [10/11/12/13/14 " aagarwa at gcc dot gnu.org 2023-06-20 19:37 ` bergner 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-91804-4-jscMwL4R5V@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).