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 11:09:58 +0000 [thread overview] Message-ID: <bug-63281-4-DdWrzhBHnK@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 --- Comment #11 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> --- While for the const which Bill said in comment9, 0x000800004100001 The code sequence still contains a few instructions: e.g. li %r11,0 ori %r11,%r11,0x8000 sldi %r11,%r11,32 oris %r11,%r11,0x410 ori %r11,%r11,0x1 std %r11,0(%r3)
next prev parent reply other threads:[~2021-12-21 11:09 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 ` [Bug rtl-optimization/63281] " guojiufu at gcc dot gnu.org 2021-12-21 11:09 ` guojiufu at gcc dot gnu.org [this message] 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-DdWrzhBHnK@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: linkBe 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).