From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Li Jia He <helijia@linux.ibm.com>,
gcc-patches@gcc.gnu.org, wschmidt@linux.ibm.com
Subject: Re: [PATCH] [RS6000] Change maddld match_operand from DI to GPR
Date: Mon, 24 Jun 2019 08:10:00 -0000 [thread overview]
Message-ID: <d2040539-8144-9c2d-98a1-441cc26bdb85@linux.ibm.com> (raw)
In-Reply-To: <20190624080218.GD7313@gate.crashing.org>
Hi Segher,
on 2019/6/24 ä¸å4:02, Segher Boessenkool wrote:
> Hi Kewen,
>
> On Mon, Jun 24, 2019 at 03:43:26PM +0800, Kewen.Lin wrote:
>> on 2019/6/24 ä¸å3:19, Segher Boessenkool wrote:
>>> Newer ISAs require 64-bit to be implemented. There are no optional
>>> 64-bit categories anymore. Since this instruction is enabled for P9
>>> (ISA 3.0) only (that's the TARGET_MODULO), it's fine.
>>>
>>> What you are saying is quite true for older CPUs/ISAs though: there you
>>> have to make sure you are targetting a CPU that supports the 64-bit
>>> categories, before using any 64-bit insns.
>>>
>>> But those days are gone :-)
>>
>> Good to know that, thanks a lot for the information! It's fine then.
>>
>> It sounds like we can have a clean up for some others like
>> TARGET_EXTSWSLI. :)
>
> Yes, but be careful there! The insn patterns for this use DImode, which
> does not mean the same thing without -mpowerpc64 (it's a register pair
> then, not what you want).
>
> And it doesn't make much sense to allow this for SImode as well (using
> GPR, perhaps), because the insn just is a shift left for SImode, and we
> already have shift left instructions.
>
> So we might want to just directly say "TARGET_MODULO && TARGET_POWERPC64"
> in those patterns (TARGET_MODULO is a funny way of saying "p9 or later").
>
Thanks for further clarification! Yes, I agree with you. I just noticed
that extswsli isn't like maddld and not suitable for SImode.
Thanks,
Kewen
>
> Segher
>
next prev parent reply other threads:[~2019-06-24 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 6:00 Li Jia He
2019-06-24 6:45 ` Kewen.Lin
2019-06-24 7:19 ` Segher Boessenkool
2019-06-24 7:43 ` Kewen.Lin
2019-06-24 7:49 ` Kewen.Lin
2019-06-24 8:16 ` Segher Boessenkool
2019-06-24 8:02 ` Segher Boessenkool
2019-06-24 8:10 ` Kewen.Lin [this message]
2019-06-24 7:39 ` Segher Boessenkool
2019-06-26 5:07 ` Li Jia He
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=d2040539-8144-9c2d-98a1-441cc26bdb85@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=helijia@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).