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/110588] btl (on x86_64) not always generated
Date: Fri, 14 Jul 2023 17:22:35 +0000	[thread overview]
Message-ID: <bug-110588-4-5BMZT724Oh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110588-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:43a0a5cd57eefd5a5bbead606ec4f6959af31802

commit r14-2528-g43a0a5cd57eefd5a5bbead606ec4f6959af31802
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Fri Jul 14 18:21:56 2023 +0100

    PR target/110588: Add *bt<mode>_setncqi_2 to generate btl on x86.

    This patch resolves PR target/110588 to catch another case in combine
    where the i386 backend should be generating a btl instruction.  This adds
    another define_insn_and_split to recognize the RTL representation for this
    case.

    I also noticed that two related define_insn_and_split weren't using the
    preferred string style for single statement preparation-statements, so
    I've reformatted these to be consistent in style with the new one.

    2023-07-14  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            PR target/110588
            * config/i386/i386.md (*bt<mode>_setcqi): Prefer string form
            preparation statement over braces for a single statement.
            (*bt<mode>_setncqi): Likewise.
            (*bt<mode>_setncqi_2): New define_insn_and_split.

    gcc/testsuite/ChangeLog
            PR target/110588
            * gcc.target/i386/pr110588.c: New test case.

  parent reply	other threads:[~2023-07-14 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 10:02 [Bug target/110588] New: " pinskia at gcc dot gnu.org
2023-07-08 21:12 ` [Bug target/110588] " roger at nextmovesoftware dot com
2023-07-09  8:08 ` ubizjak at gmail dot com
2023-07-14 17:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-23  5:06 ` roger at nextmovesoftware dot com

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-110588-4-5BMZT724Oh@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).