public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102239] powerpc suboptimal boolean test of contiguous bits Date: Tue, 11 Jan 2022 09:23:01 +0000 [thread overview] Message-ID: <bug-102239-4-p8q2ImUmiS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102239-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102239 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Xiong Hu Luo <luoxhu@gcc.gnu.org>: https://gcc.gnu.org/g:19d81fda48f30c4fc11c8912749351acd9159c17 commit r12-6433-g19d81fda48f30c4fc11c8912749351acd9159c17 Author: Xionghu Luo <luoxhu@linux.ibm.com> Date: Sun Dec 12 23:17:13 2021 -0600 rs6000: powerpc suboptimal boolean test of contiguous bits [PR102239] Add specialized version to combine two instructions from 9: {r123:CC=cmp(r124:DI&0x600000000,0);clobber scratch;} REG_DEAD r124:DI 10: pc={(r123:CC==0)?L15:pc} REG_DEAD r123:CC to: 10: {pc={(r123:DI&0x600000000==0)?L15:pc};clobber scratch;clobber %0:CC;} then split2 will split it to one rotate dot instruction (to save one rotate back instruction) as shifted result doesn't matter when comparing to 0 in CCEQmode. Bootstrapped and regression tested pass on Power 8/9/10. gcc/ChangeLog: PR target/102239 * config/rs6000/rs6000-protos.h (rs6000_is_valid_rotate_dot_mask): New declare. * config/rs6000/rs6000.c (rs6000_is_valid_rotate_dot_mask): New function. * config/rs6000/rs6000.md (*branch_anddi3_dot): New. gcc/testsuite/ChangeLog: PR target/102239 * gcc.target/powerpc/pr102239.c: New test.
next prev parent reply other threads:[~2022-01-11 9:23 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-08 11:55 [Bug c/102239] New: " npiggin at gmail dot com 2021-09-09 19:40 ` [Bug target/102239] " segher at gcc dot gnu.org 2021-11-24 7:17 ` luoxhu at gcc dot gnu.org 2021-11-24 23:22 ` segher at gcc dot gnu.org 2021-11-26 8:50 ` luoxhu at gcc dot gnu.org 2021-11-26 15:53 ` segher at gcc dot gnu.org 2021-11-29 3:31 ` luoxhu at gcc dot gnu.org 2021-11-29 6:36 ` luoxhu at gcc dot gnu.org 2021-11-29 10:05 ` segher at gcc dot gnu.org 2021-11-30 5:28 ` luoxhu at gcc dot gnu.org 2021-11-30 22:59 ` segher at gcc dot gnu.org 2021-12-01 7:46 ` luoxhu at gcc dot gnu.org 2022-01-11 9:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-12 0:27 ` luoxhu 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-102239-4-p8q2ImUmiS@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).