public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.seifert at de dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/93176] PPC: inefficient 64-bit constant consecutive ones Date: Fri, 18 Aug 2023 06:10:03 +0000 [thread overview] Message-ID: <bug-93176-4-J5iJuGgnNj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93176-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93176 --- Comment #10 from Jens Seifert <jens.seifert at de dot ibm.com> --- Looks like no patch in the area got delivered. I did a small test for unsigned long long c0000FFFF00000000() { return 0x0000FFFF00000000ULL; } gcc 13.2.0: li 3,0 ori 3,3,0xffff sldi 3,3,32 expected: li 3, -1 rldic 3, 3, 32, 16 All consecutive ones can be created with li + rldic. The rotate eliminates the bits on the right and the clear the bits on the left as described below: li t,-1 rldic d,T,MB,63-ME
next prev parent reply other threads:[~2023-08-18 6:10 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93176-4@http.gcc.gnu.org/bugzilla/> 2020-09-10 22:00 ` bergner at gcc dot gnu.org 2020-09-29 1:15 ` bergner at gcc dot gnu.org 2020-11-18 18:15 ` bergner at gcc dot gnu.org 2020-11-19 3:56 ` amodra at gmail dot com 2023-08-16 10:35 ` jens.seifert at de dot ibm.com 2023-08-18 0:52 ` amodra at gmail dot com 2023-08-18 2:47 ` bergner at gcc dot gnu.org 2023-08-18 6:10 ` jens.seifert at de dot ibm.com [this message] 2023-08-18 6:14 ` sjames at gcc dot gnu.org 2023-08-18 6:20 ` guojiufu at gcc dot gnu.org 2023-08-18 16:07 ` bergner at gcc dot gnu.org 2023-10-08 2:36 ` 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-93176-4-J5iJuGgnNj@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).