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: Wed, 30 Jun 2021 19:04:34 +0000	[thread overview]
Message-ID: <bug-101260-4-B6vvaozTaC@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 #7 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> ---
I had a look at the optimized tree output which looks good to me. However, I
see that 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 might be wrong. If I swap r10 by r11 via

diff --git a/gcc/config/s390/s390.md b/gcc/config/s390/s390.md
index 7faf775fbf2..0319934062a 100644
--- a/gcc/config/s390/s390.md
+++ b/gcc/config/s390/s390.md
@@ -1747,8 +1747,8 @@
    (set (match_dup 3) (unspec:DI [(match_dup 5) (const_int 1)]
                                 UNSPEC_VEC_EXTRACT))]
 {
-  operands[2] = operand_subword (operands[0], 0, 0, TImode);
-  operands[3] = operand_subword (operands[0], 1, 0, TImode);
+  operands[2] = operand_subword (operands[0], 1, 0, TImode);
+  operands[3] = operand_subword (operands[0], 0, 0, TImode);
   operands[4] = gen_rtx_REG (DImode, REGNO (operands[1]));
   operands[5] = gen_rtx_REG (V2DImode, REGNO (operands[1]));
 })

then the compiled program just runs fine. However, I'm not sure whether this
fixes the problem or just the symptoms. I will come back to this tomorrow.

  parent reply	other threads:[~2021-06-30 19:04 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 [this message]
2021-07-01 16:58 ` stefansf at linux dot ibm.com
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-B6vvaozTaC@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: link
Be 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).