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/108933] [11/12/13/14 Regression] Missing rev16 detection
Date: Mon, 29 Jan 2024 15:58:33 +0000	[thread overview]
Message-ID: <bug-108933-4-0iuPPXHqDT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108933-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>:

https://gcc.gnu.org/g:bad991a1c5960e90c4686a9362a1258ef29e195b

commit r14-8499-gbad991a1c5960e90c4686a9362a1258ef29e195b
Author: Matthieu Longo <matthieu.longo@arm.com>
Date:   Mon Jan 29 15:54:35 2024 +0000

    arm: Add pattern for bswap + rotate -> rev16 [Bug 108933]

    The rev16 pattern was not recognised anymore as a change in the bswap
    tree pass was introducing a new GIMPLE form, not recognized by the
    assembly final transformation pass.

    Also, fix the output patterns for arm_rev16si_alt[12] to correctly
    handle the instructions being made conditional.

    More details in the PR.

    gcc/ChangeLog:

            PR target/108933
            * config/arm/arm.md (arm_rev16si2): Convert to define_insn.
            Correct generated RTL.
            (arm_rev16si2_alt1): Correctly handle conditional execution.
            (arm_rev16si2_alt2): Likewise.

    gcc/testsuite/ChangeLog:

            PR target/108933
            * gcc.target/arm/rev16.c: Moved to...
            * gcc.target/arm/rev16_1.c: ...here.
            * gcc.target/arm/rev16_2.c: New test to check that rev16 is
emitted.

  parent reply	other threads:[~2024-01-29 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 19:50 [Bug target/108933] New: [10/11/12/13 Regression] Missing bswap detection pinskia at gcc dot gnu.org
2023-02-25 19:51 ` [Bug target/108933] " pinskia at gcc dot gnu.org
2023-03-10 17:54 ` pinskia at gcc dot gnu.org
2023-03-15 11:44 ` jakub at gcc dot gnu.org
2023-03-15 22:09 ` [Bug target/108933] [10/11/12/13 Regression] Missing rev16 detection pinskia at gcc dot gnu.org
2023-03-15 22:10 ` pinskia at gcc dot gnu.org
2023-03-27 10:56 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug target/108933] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-01-29 15:58 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-29 16:01 ` [Bug target/108933] [11/12/13 " rearnsha 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-108933-4-0iuPPXHqDT@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).