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 middle-end/114319] htobe64-like function is not optimized on 32-bit x86
Date: Wed, 13 Mar 2024 14:35:54 +0000	[thread overview]
Message-ID: <bug-114319-4-4oTtFpaobg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114319-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:74bca21db31e3f4ab6543b56c3f26b4dfe586fef

commit r14-9453-g74bca21db31e3f4ab6543b56c3f26b4dfe586fef
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Mar 13 15:34:59 2024 +0100

    store-merging: Match bswap64 on 32-bit targets with bswapsi2 [PR114319]

    gimple-ssa-store-merging.cc tests bswap_optab in 3 different places,
    in 2 of them it has special exception for double-word bswap using pair
    of word-mode bswap optabs, but in the last one it doesn't.

    The following patch changes even the last spot.
    We don't handle 128-bit bswaps in the passes at all, because currently we
    just use uint64_t to represent the byte reshuffling (we'd need to use
    offset_int or something like that instead) and we don't have
    __builtin_bswap128 nor type-generic __builtin_bswap, so there is nothing
    for 64-bit targets there.

    2024-03-13  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/114319
            * gimple-ssa-store-merging.cc
            (imm_store_chain_info::try_coalesce_bswap): For 32-bit targets
            allow matching __builtin_bswap64 if there is bswapsi2 optab.

            * gcc.target/i386/pr114319.c: New test.

  parent reply	other threads:[~2024-03-13 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 17:45 [Bug target/114319] New: " pali at kernel dot org
2024-03-12 17:49 ` [Bug middle-end/114319] " pinskia at gcc dot gnu.org
2024-03-12 17:56 ` pinskia at gcc dot gnu.org
2024-03-12 18:04 ` pinskia at gcc dot gnu.org
2024-03-12 18:07 ` pali at kernel dot org
2024-03-12 18:10 ` pinskia at gcc dot gnu.org
2024-03-13  9:47 ` rguenth at gcc dot gnu.org
2024-03-13 14:35 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-13 14:38 ` jakub at gcc dot gnu.org
2024-03-13 21:31 ` pali at kernel dot 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-114319-4-4oTtFpaobg@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).