public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/7061] Access of bytes in struct parameters
Date: Mon, 27 Jun 2022 06:49:24 +0000	[thread overview]
Message-ID: <bug-7061-4-6IDmtQ6Nol@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-7061-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:64d4f27a0ce47e97867512bda7fa5683acf8a134

commit r13-1282-g64d4f27a0ce47e97867512bda7fa5683acf8a134
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Mon Jun 27 07:47:40 2022 +0100

    Implement __imag__ of float _Complex using shufps on x86_64.

    This patch is a follow-up improvement to my recent patch for
    PR rtl-optimization/7061.  That patch added the test case
    gcc.target/i386/pr7061-2.c:

    float im(float _Complex a) { return __imag__ a; }

    For which GCC on x86_64 currently generates:

            movq    %xmm0, %rax
            shrq    $32, %rax
            movd    %eax, %xmm0
            ret

    but with this patch we now generate (the same as LLVM):

            shufps  $85, %xmm0, %xmm0
            ret

    This is achieved by providing a define_insn_and_split that allows
    truncated lshiftrt:DI by 32 to be performed on either SSE or general
    regs, where if the register allocator prefers to use SSE, we split
    to a shufps_v4si, or if not, we use a regular shrq.

    2022-06-27  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            PR rtl-optimization/7061
            * config/i386/i386.md (*highpartdisi2): New define_insn_and_split.

    gcc/testsuite/ChangeLog
            PR rtl-optimization/7061
            * gcc.target/i386/pr7061-2.c: Update to look for shufps.

  parent reply	other threads:[~2022-06-27  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-7061-4@http.gcc.gnu.org/bugzilla/>
2021-09-22 20:26 ` gabravier at gmail dot com
2022-05-30 20:40 ` cvs-commit at gcc dot gnu.org
2022-06-10 14:20 ` cvs-commit at gcc dot gnu.org
2022-06-11 13:29 ` david.bolvansky at gmail dot com
2022-06-27  6:49 ` cvs-commit at gcc dot gnu.org [this message]
     [not found] <bug-7061-695@http.gcc.gnu.org/bugzilla/>
2005-11-02  8:09 ` rth at gcc dot gnu dot org
2006-02-08 21:10 ` pluto at agmk dot net

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-7061-4-6IDmtQ6Nol@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).