public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jiufu Guo <guojiufu@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com, linkw@gcc.gnu.org
Subject: Re: [PATCH V4 1/2] rs6000: use li;x?oris to build constant
Date: Mon, 19 Dec 2022 17:16:49 +0800	[thread overview]
Message-ID: <7epmcfiwhq.fsf@pike.rch.stglabs.ibm.com> (raw)
In-Reply-To: <20221216211625.GI25951@gate.crashing.org> (Segher Boessenkool's message of "Fri, 16 Dec 2022 15:16:25 -0600")

Hi,

Segher Boessenkool <segher@kernel.crashing.org> writes:

> Hi!
>
> On Mon, Dec 12, 2022 at 09:38:28AM +0800, Jiufu Guo wrote:
>> 	PR target/106708
>> 
>> gcc/ChangeLog:
>> 
>> 	* config/rs6000/rs6000.cc (rs6000_emit_set_long_const): Add using
>> 	"li; x?oris" to build constant.
>> 
>> gcc/testsuite/ChangeLog:
>> 
>> 	* gcc.target/powerpc/pr106708.c: New test.
>
> Okay for trunk with the nits Ke Wen pointed out taken care off.

Thanks! Updated and committed via r13-4771-g97a8e88cd7d225.

BR,
Jeff (Jiufu)
>
> Thanks!
>
>
> Segher

      reply	other threads:[~2022-12-19  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  1:38 Jiufu Guo
2022-12-12  1:38 ` [PATCH V4 2/2] " Jiufu Guo
2023-01-04  6:11   ` Jiufu Guo
2023-02-20  4:41     ` Ping^^ " Jiufu Guo
2023-04-26  2:35       ` Ping^^^ " Jiufu Guo
2023-05-15  6:53   ` Kewen.Lin
2023-05-17  2:17     ` guojiufu
2022-12-14 10:27 ` [PATCH V4 1/2] " Kewen.Lin
2022-12-15  3:29   ` Jiufu Guo
2022-12-16 21:12   ` Segher Boessenkool
2022-12-16 21:16 ` Segher Boessenkool
2022-12-19  9:16   ` Jiufu Guo [this message]

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=7epmcfiwhq.fsf@pike.rch.stglabs.ibm.com \
    --to=guojiufu@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).