public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36557] -m32 -mpowerpc64 produces better code than -m64 for a!=0
Date: Tue, 05 Mar 2024 00:28:10 +0000 [thread overview]
Message-ID: <bug-36557-4-brLMMm0OnG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36557-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36557
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |bergner at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #4)
> We now do
>
> cntlzw 3,3
> srwi 3,3,5
> xori 3,3,0x1
> blr
>
> which is still not optimal (and not what -m32 / -m32 -mpowerpc64 do).
My GCC 10 and later compiles show we now generate:
addic 9,3,-1
subfe 3,9,3
blr
Marking as FIXED.
prev parent reply other threads:[~2024-03-05 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-36557-4@http.gcc.gnu.org/bugzilla/>
2012-09-26 5:34 ` segher at gcc dot gnu.org
2014-12-26 21:56 ` segher at gcc dot gnu.org
2015-01-08 3:47 ` segher at gcc dot gnu.org
2024-03-05 0:28 ` bergner 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-36557-4-brLMMm0OnG@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).