public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "munroesj at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100085] Bad code for union transfer from __float128 to vector types
Date: Fri, 25 Feb 2022 15:31:54 +0000	[thread overview]
Message-ID: <bug-100085-4-95c7Xbi4GZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100085-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100085

--- Comment #21 from Steven Munroe <munroesj at gcc dot gnu.org> ---
Yes I was told by Peter Bergner that the fix from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100085#c15 had been back ported
top AT15.0-1.

But when ran this test with AT15.0-1 I saw:

0000000000000000 <test_xfer_bin128_2_vui32t_V0>:
   0:   20 00 20 39     li      r9,32
   4:   d0 ff 41 39     addi    r10,r1,-48
   8:   57 12 42 f0     xxswapd vs34,vs34
   c:   99 4f 4a 7c     stxvd2x vs34,r10,r9
  10:   ce 48 4a 7c     lvx     v2,r10,r9
  14:   20 00 80 4e     blr

0000000000000030 <test_xfer_bin128_2_vui64t_V0>:
  30:   20 00 20 39     li      r9,32
  34:   d0 ff 41 39     addi    r10,r1,-48
  38:   57 12 42 f0     xxswapd vs34,vs34
  3c:   99 4f 4a 7c     stxvd2x vs34,r10,r9
  40:   ce 48 4a 7c     lvx     v2,r10,r9
  44:   20 00 80 4e     blr

0000000000000060 <test_xfer_bin128_2_vui128t_V0>:
  60:   20 00 20 39     li      r9,32
  64:   d0 ff 41 39     addi    r10,r1,-48
  68:   57 12 42 f0     xxswapd vs34,vs34
  6c:   99 4f 4a 7c     stxvd2x vs34,r10,r9
  70:   99 4e 4a 7c     lxvd2x  vs34,r10,r9
  74:   57 12 42 f0     xxswapd vs34,vs34
  78:   20 00 80 4e     blr

0000000000000090 <test_xfer_bin128_2_ui128t_V0>:
  90:   57 12 42 f0     xxswapd vs34,vs34
  94:   20 00 40 39     li      r10,32
  98:   d0 ff 01 39     addi    r8,r1,-48
  9c:   f0 ff 21 39     addi    r9,r1,-16
  a0:   99 57 48 7c     stxvd2x vs34,r8,r10
  a4:   00 00 69 e8     ld      r3,0(r9)
  a8:   08 00 89 e8     ld      r4,8(r9)
  ac:   20 00 80 4e     blr

So either the patch for AT15.0-1 is not applied correctly or is non-functional
because of some difference between GCC11/GCC12. Or regressed because of some
other change/patch.

In my experience this part of GCC is fragile (based on the long/sad history of
IBM long double). So this needs to monitored with each new update.

  parent reply	other threads:[~2022-02-25 15:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 18:19 [Bug rtl-optimization/100085] New: " munroesj at gcc dot gnu.org
2021-04-14 18:22 ` [Bug rtl-optimization/100085] " munroesj at gcc dot gnu.org
2021-04-15  6:59 ` [Bug target/100085] " rguenth at gcc dot gnu.org
2021-04-15 18:41 ` segher at gcc dot gnu.org
2021-04-16 20:30 ` munroesj at gcc dot gnu.org
2021-04-29 15:04 ` munroesj at gcc dot gnu.org
2021-04-30 19:52 ` bergner at gcc dot gnu.org
2021-05-24  6:41 ` luoxhu at gcc dot gnu.org
2021-05-24 21:49 ` segher at gcc dot gnu.org
2021-06-02  8:27 ` luoxhu at gcc dot gnu.org
2021-06-09  5:13 ` luoxhu at gcc dot gnu.org
2021-06-09 21:35 ` bergner at gcc dot gnu.org
2021-06-09 22:08 ` segher at gcc dot gnu.org
2021-06-10 15:00 ` munroesj at gcc dot gnu.org
2021-06-11 20:28 ` segher at gcc dot gnu.org
2022-01-14 17:17 ` wschmidt at gcc dot gnu.org
2022-02-24 20:48 ` munroesj at gcc dot gnu.org
2022-02-24 20:53 ` munroesj at gcc dot gnu.org
2022-02-24 21:17 ` segher at gcc dot gnu.org
2022-02-24 21:22 ` segher at gcc dot gnu.org
2022-02-24 21:26 ` segher at gcc dot gnu.org
2022-02-25 15:31 ` munroesj at gcc dot gnu.org [this message]
2022-02-25 22:57 ` segher at gcc dot gnu.org
2022-02-26 16:22 ` munroesj 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-100085-4-95c7Xbi4GZ@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).