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/106708] [rs6000] 64bit constant generation with oris xoris
Date: Wed, 17 May 2023 02:13:30 +0000	[thread overview]
Message-ID: <bug-106708-4-XEXwVAjiTF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106708-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106708

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>:

https://gcc.gnu.org/g:5eb7d560626e427673c53723ed430c4bb5721f33

commit r14-923-g5eb7d560626e427673c53723ed430c4bb5721f33
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Sat Dec 10 21:18:51 2022 +0800

    rs6000: use lis;xoris to build constant

    For constant C:
    If '(c & 0xFFFFFFFF0000FFFFULL) == 0xFFFFFFFF00000000' or say:
    32(1) || 1(0) || 15(x) || 16(0), we could use "lis; xoris" to build.

    Here N(M) means N continuous bit M, x for M means it is ok for either
    1 or 0; '||' means concatenation.

    This patch update rs6000_emit_set_long_const to support those constants.

    Compare with previous version:
    https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608292.html
    This patch updates test function names only.

    Bootstrap and regtest pass on ppc64{,le}.

            PR target/106708

    gcc/ChangeLog:

            * config/rs6000/rs6000.cc (rs6000_emit_set_long_const): Support
building
            constants through "lis; xoris".

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr106708.c: Add test function.

  parent reply	other threads:[~2023-05-17  2:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-106708-4@http.gcc.gnu.org/bugzilla/>
2022-12-07  2:39 ` guojiufu at gcc dot gnu.org
2022-12-19 10:32 ` cvs-commit at gcc dot gnu.org
2023-05-10  9:10 ` guojiufu at gcc dot gnu.org
2023-05-17  2:13 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-08  2:30 ` 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-106708-4-XEXwVAjiTF@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).