public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seiko at imavr dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104590] New: ppc64: even/odd permutation for VSX 64-bit to 32-bit conversions is no longer necessary.
Date: Fri, 18 Feb 2022 08:35:23 +0000	[thread overview]
Message-ID: <bug-104590-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104590
           Summary: ppc64: even/odd permutation for VSX 64-bit to 32-bit
                    conversions is no longer necessary.
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seiko at imavr dot com
  Target Milestone: ---

Created attachment 52473
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52473&action=edit
proposal patch remove the extra shuffles

The following VSX intrinsics did not need to exist in the first place, and they
must be replaced or renamed by convinced names suitable to the mapped
instructions or at least modified by removing the unnecessary shuffles:

- vector unsigned int vec_unsignede(vector double) -> xvcvdpuxws
- vector unsigned int vec_unsignedo(vector double) -> xvcvdpuxws
- vector float vec_floate(vector double) -> xvcvdpsp
- vector float vec_floato(vector double) -> xvcvdpsp
- vector float vec_floate(vector signed long long) -> xvcvsxdsp
- vector float vec_floato(vector signed long long) -> xvcvsxdsp
- vector float vec_floate(vector unsigned long long) -> xvcvuxdsp
- vector float vec_floato(vector unsigned long long) -> xvcvuxdsp

According to the latest update of ISA 3.1:

Previous versions of the architecture allowed the contents of bits 32:63 of
each doubleword in the result register to be undefined, however, all processors
that support this instruction write the result into bits 32:63 of each
doubleword in the result register
as well as into bits 0:31, as is required by this version of the architecture.

             reply	other threads:[~2022-02-18  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  8:35 seiko at imavr dot com [this message]
2022-02-18  8:42 ` [Bug target/104590] " seiko at imavr dot com
2022-02-18 12:21 ` segher 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-104590-4@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).