public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefansf at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101260] [10/11 Regression] Backport 27381e78925 to GCC 11 Date: Thu, 01 Jul 2021 16:58:57 +0000 [thread overview] Message-ID: <bug-101260-4-PEmLBk6Bbo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101260-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260 --- Comment #8 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> --- Pass split2 transforms (insn 218 222 114 15 (set (reg/v:TI 10 %r10 [orig:87 a ] [87]) (reg/v:TI 18 %f4 [orig:87 a ] [87])) 1466 {movti} (nil)) into (insn 234 222 235 15 (set (reg:DI 10 %r10 [ a ]) (reg:DI 18 %f4)) 1467 {*movdi_64} (nil)) (insn 235 234 114 15 (set (reg:DI 11 %r11 [orig:87 a+8 ] [87]) (unspec:DI [ (reg:V2DI 18 %f4) (const_int 1 [0x1]) ] UNSPEC_VEC_EXTRACT)) 495 {*vec_extractv2di} (nil)) which is then transformed by cprop_hardreg into (insn 234 222 235 14 (set (reg:DI 10 %r10 [ a ]) (reg:DI 11 %r11 [18])) 1467 {*movdi_64} (expr_list:REG_DEAD (reg:DI 11 %r11 [18]) (nil))) (insn 235 234 114 14 (set (reg:DI 11 %r11 [orig:87 a+8 ] [87]) (unspec:DI [ (reg:V2DI 18 %f4) (const_int 1 [0x1]) ] UNSPEC_VEC_EXTRACT)) 495 {*vec_extractv2di} (expr_list:REG_DEAD (reg:V2DI 18 %f4) (nil))) where in insn 234 register f4 is substituted by r11 which is wrong. This can also be observed in the final assembler output: vlvgp %v4,%r10,%r11 l %r2,12(%r1) ahi %r2,-1 st %r2,12(%r1) cijhe %r2,0,.L13 lgr %r10,%r11 // (*) vlgvg %r11,%v4,1 Registers r10 and r11 are moved into v4. The inverse move from v4 into r10 and r11 is broken since cprop_hardreg wrongly substitutes f4 by r11. Thus the expected output for (*) is: lgdr %r10,%f4
next prev parent reply other threads:[~2021-07-01 16:58 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-29 15:35 [Bug tree-optimization/101260] New: " stefansf at linux dot ibm.com 2021-06-29 23:08 ` [Bug tree-optimization/101260] " jakub at gcc dot gnu.org 2021-06-30 6:33 ` rguenth at gcc dot gnu.org 2021-06-30 7:41 ` stefansf at linux dot ibm.com 2021-06-30 7:58 ` [Bug tree-optimization/101260] [10/11 Regression] " rguenth at gcc dot gnu.org 2021-06-30 14:08 ` stefansf at linux dot ibm.com 2021-06-30 17:23 ` jakub at gcc dot gnu.org 2021-06-30 19:04 ` stefansf at linux dot ibm.com 2021-07-01 16:58 ` stefansf at linux dot ibm.com [this message] 2021-07-06 6:53 ` [Bug rtl-optimization/101260] " rguenth at gcc dot gnu.org 2021-07-19 12:02 ` [Bug rtl-optimization/101260] [10/11/12 " rguenth at gcc dot gnu.org 2021-08-06 13:59 ` stefansf at linux dot ibm.com 2022-01-14 19:24 ` [Bug rtl-optimization/101260] [10/11/12 Regression] regcprop: Determine subreg offset depending on endianness pinskia at gcc dot gnu.org 2022-01-14 19:26 ` pinskia at gcc dot gnu.org 2022-01-14 19:27 ` pinskia at gcc dot gnu.org 2022-01-14 19:32 ` pinskia at gcc dot gnu.org 2022-01-14 19:33 ` pinskia at gcc dot gnu.org 2022-01-14 19:37 ` pinskia at gcc dot gnu.org 2022-02-01 12:35 ` cvs-commit at gcc dot gnu.org 2022-06-09 8:53 ` [Bug rtl-optimization/101260] [10/11 " stefansf at linux dot ibm.com 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug rtl-optimization/101260] [11 " 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-101260-4-PEmLBk6Bbo@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).