public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63281] powerpc64le creates 64 bit constants from scratch instead of loading them
Date: Tue, 21 Dec 2021 09:23:01 +0000 [thread overview]
Message-ID: <bug-63281-4-bvPyDawvQ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63281-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63281
Jiu Fu Guo <guojiufu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |guojiufu at gcc dot gnu.org
--- Comment #10 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
With the latest trunk (AT14 is similar), the generated code looks like this:
-O
lis %r9,0x8123
ori %r9,%r9,0x4567
rldimi %r9,%r9,32,0
std %r9,0(%r10)
Or
-O3
lis %r11,0x1234
lis %r31,0x2345
lis %r12,0x3456
ori %r11,%r11,0x5678
ori %r31,%r31,0x6781
ori %r12,%r12,0x7812
rldimi %r11,%r11,32,0
rldimi %r31,%r31,32,0
rldimi %r12,%r12,32,0
...
This code seems better than the previous one.
next prev parent reply other threads:[~2021-12-21 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 23:01 [Bug target/63281] New: " anton at samba dot org
2014-09-17 6:32 ` [Bug target/63281] " amodra at gmail dot com
2014-09-17 6:40 ` amodra at gmail dot com
2021-12-21 9:23 ` guojiufu at gcc dot gnu.org [this message]
2021-12-21 11:09 ` [Bug rtl-optimization/63281] " guojiufu at gcc dot gnu.org
2021-12-21 14:29 ` segher at gcc dot gnu.org
2021-12-21 14:36 ` segher at gcc dot gnu.org
2021-12-30 3:29 ` guojiufu at gcc dot gnu.org
2021-12-30 7:14 ` amodra at gmail dot com
2021-12-31 1:51 ` guojiufu at gcc dot gnu.org
2021-12-31 2:00 ` guojiufu at gcc dot gnu.org
2021-12-31 7:33 ` segher at gcc dot gnu.org
2022-01-04 6:07 ` guojiufu at gcc dot gnu.org
2022-01-04 8:06 ` guojiufu at gcc dot gnu.org
2022-01-06 10:06 ` guojiufu at gcc dot gnu.org
2022-01-10 6:52 ` guojiufu 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-63281-4-bvPyDawvQ5@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).