public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42587] bswap not recognized for memory
Date: Sat, 08 May 2021 13:17:06 +0000 [thread overview]
Message-ID: <bug-42587-4-3GrSg9G5xn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42587-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42587
Peter Cordes <peter at cordes dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |peter at cordes dot ca
--- Comment #12 from Peter Cordes <peter at cordes dot ca> ---
(In reply to Andi Kleen from comment #11)
> Only when the first test case is fixed too
https://godbolt.org/z/7M8cx3vT1 GCC8.1 -O3 for x86-64
push rbx
mov ebx, edi
call acpi_ut_track_stack_ptr
mov eax, ebx
pop rbx
bswap eax
ret
The code in the initial report optimizes to bswap with GCC8.1 and later.
Is that the test case you meant? GCC8.1 was released on May 2, 2018, well
before your Nov comment, so maybe you meant something else.
next prev parent reply other threads:[~2021-05-08 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42587-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:51 ` xiaoyuanbo at yeah dot net
2021-05-08 13:17 ` peter at cordes dot ca [this message]
2021-05-09 21:02 ` andi at firstfloor dot org
2021-05-10 12:21 ` cvs-commit at gcc dot gnu.org
2021-05-10 12:22 ` hjl.tools at gmail dot com
2010-01-03 6:15 [Bug tree-optimization/42587] New: bswap not recognized for union andi-gcc at firstfloor dot org
2010-01-03 10:58 ` [Bug tree-optimization/42587] bswap not recognized for memory rguenth at gcc dot gnu dot org
2010-01-03 16:01 ` rguenth at gcc dot gnu dot org
2010-01-03 16:26 ` rguenth at gcc dot gnu dot org
2010-01-06 14:07 ` jamborm at gcc dot gnu dot org
2010-02-27 20:04 ` rguenth at gcc dot gnu 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-42587-4-3GrSg9G5xn@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).