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 target/78904] zero-extracts are not effective
Date: Thu, 16 Nov 2023 18:13:00 +0000	[thread overview]
Message-ID: <bug-78904-4-o0fZ3KsU48@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78904-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:

https://gcc.gnu.org/g:8ebc7e0b0ddf4679cf09ed6836fac30ca01d3ba0

commit r14-5539-g8ebc7e0b0ddf4679cf09ed6836fac30ca01d3ba0
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Thu Nov 16 18:07:36 2023 +0100

    i386: Optimize QImode insn with high input registers

    Sometimes the compiler emits the following code with <insn>qi_ext<mode>_0:

            shrl    $8, %eax
            addb    %bh, %al

    Patch introduces new low part QImode insn patterns with both of
    their input arguments extracted from high register.  This invalid
    insn is split after reload to a move from the high register
    and <insn>qi_ext<mode>_0 instruction.  The combine pass is able to
    convert shift to zero/sign-extract sub-RTX, which we split to the
    optimal:

            movzbl  %bh, %edx
            addb    %ah, %dl

            PR target/78904

    gcc/ChangeLog:

            * config/i386/i386.md (*addqi_ext2<mode>_0):
            New define_insn_and_split pattern.
            (*subqi_ext2<mode>_0): Ditto.
            (*<code>qi_ext2<mode>_0): Ditto.

    gcc/testsuite/ChangeLog:

            * gcc.target/i386/pr78904-10.c: New test.
            * gcc.target/i386/pr78904-10a.c: New test.
            * gcc.target/i386/pr78904-10b.c: New test.

      parent reply	other threads:[~2023-11-16 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-78904-4@http.gcc.gnu.org/bugzilla/>
2023-04-19 15:04 ` cvs-commit at gcc dot gnu.org
2023-06-23  8:22 ` roger at nextmovesoftware dot com
2023-06-23 17:47 ` segher at gcc dot gnu.org
2023-06-24 22:12 ` cvs-commit at gcc dot gnu.org
2023-11-14 17:36 ` cvs-commit at gcc dot gnu.org
2023-11-15 21:22 ` cvs-commit at gcc dot gnu.org
2023-11-16 18:13 ` cvs-commit at gcc dot gnu.org [this message]

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-78904-4-o0fZ3KsU48@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).