From: Ajit Agarwal <aagarwa1@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
"Kewen.Lin" <linkw@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH v2] rs6000: Add new pass for replacement of contiguous addresses vector load lxv with lxvp
Date: Wed, 29 Nov 2023 19:40:26 +0530 [thread overview]
Message-ID: <31d34b12-c926-490f-a0f6-837c99e84fb0@linux.ibm.com> (raw)
In-Reply-To: <ZWYKDnLnFEZqxvms@cowardly-lion.the-meissners.org>
Hello All:
I am working on fixing the below issues and incorporating comments from Kewen and
Michael.
Thanks & Regards
Ajit
On 28/11/23 9:11 pm, Michael Meissner wrote:
> On Tue, Nov 28, 2023 at 05:44:43PM +0800, Kewen.Lin wrote:
>> on 2023/11/28 15:05, Michael Meissner wrote:
>>> I tried using this patch to compare with the vector size attribute patch I
>>> posted. I could not build it as a cross compiler on my x86_64 because the
>>> assembler gives the following error:
>>>
>>> Error: operand out of domain (11 is not a multiple of 2) for
>>> std_stacktrace-elf.o. If you look at the assembler, it has combined a lxvp 11
>>> and lxvp 12 into:
>>>
>>> lxvp 11,0(9)
>>>
>>> The powerpc architecture requires that registers that are loaded with load
>>> vector pair and stored with store vector point instructions only load/store
>>> even/odd register pairs, and not odd/even pairs. Unfortunately, it will mean
>>> that this optimization will match less often.
>>>
>>
>> Yes, the current implementation need some refinements, as comments in [1]:
>>
>>> Besides, it seems a bad idea to put this pass after reload? as register allocation
>>> finishes, this pairing has to be restricted by the reg No. (I didn't see any
>>> checking on the reg No. relationship for paring btw.)
>>>
>>> Looking forward to the comments from Segher/David/Peter/Mike etc.
>>
>> I wonder if we should consider running such pass before reload instead.
>>
>> [1] https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638070.html
>>
>> BR,
>> Kewen
>
> If I add code to check if the target register is even, then the following
> fails:
>
> /home/meissner/fsf-src/work148-ajit/libquadmath/math/erfq.c: In function ‘erfcq’:
> /home/meissner/fsf-src/work148-ajit/libquadmath/math/erfq.c:943:1: error: insn does not satisfy its constraints:
> 943 | }
> | ^
> (insn 1087 1939 1088 66 (set (reg/v:KF 74 10 [orig:643 y ] [643])
> (fma:KF (reg/v:KF 64 0 [orig:153 z ] [153])
> (reg/v:KF 65 1 [orig:639 y ] [639])
> (reg:KF 76 12 [orig:642 MEM[(const _Float128 *)p_276 + 16B] ] [642]))) "/home/meissner/fsf-src/work148-ajit/libquadmath/math/erfq.c":112:9 1004 {fmakf4_hw}
> (expr_list:REG_DEAD (reg/v:KF 65 1 [orig:639 y ] [639])
> (nil)))
>
> In particular, the IEEE 128-bit arithmetic functions require Altivec registers.
> So we would need to make sure the new insns all meet their constraints.
>
> I tend to think that it would be desirable to do it before reload. But then we
> will need to check if extra moves are generated. I suspect we will need
> Peter's patch to allow 128-bit types that are subregs of OOmode. I.e., the
> code generated would change:
>
> (set (reg:MODE1 tmp-reg)
> (mem ...+8))
>
> (set (reg:MODE2 tmp-reg+1)
> (mem ...))
>
> to:
>
> (set (reg:OO vp-reg)
> (mem ...))
>
> (set (reg:MODE1 tmp-reg)
> (subreg:MODE1 (reg:OO vp-reg 0)))
>
> (set (reg:MODE2 tmp-reg+1)
> (subreg:MODE2 (reg:OO vp-reg 16)))
>
> Note, I may have the offsets and register numbers backwards in terms of endian.
>
next prev parent reply other threads:[~2023-11-29 14:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 19:04 Ajit Agarwal
2023-10-15 12:13 ` [PING ^0][PATCH " Ajit Agarwal
2023-10-23 8:32 ` [PING ^1][PATCH " Ajit Agarwal
2023-11-10 7:04 ` [PING ^2][PATCH " Ajit Agarwal
2023-11-24 9:31 ` [PATCH " Kewen.Lin
2023-11-28 4:34 ` Michael Meissner
2023-11-28 9:33 ` Kewen.Lin
2023-12-01 9:10 ` Ajit Agarwal
2023-12-04 2:01 ` Kewen.Lin
2023-12-05 13:43 ` Ajit Agarwal
2023-12-05 18:01 ` Ajit Agarwal
2023-12-06 2:22 ` Kewen.Lin
2023-12-06 5:09 ` Michael Meissner
2023-12-07 7:14 ` Kewen.Lin
2023-12-07 11:01 ` Ajit Agarwal
2023-12-08 8:01 ` Ajit Agarwal
2023-12-08 9:51 ` Kewen.Lin
2023-12-12 6:28 ` Kewen.Lin
2023-12-12 7:38 ` Ajit Agarwal
2023-11-28 7:05 ` Michael Meissner
2023-11-28 9:44 ` Kewen.Lin
2023-11-28 15:41 ` Michael Meissner
2023-11-29 14:10 ` Ajit Agarwal [this message]
2023-12-01 9:13 ` Ajit Agarwal
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=31d34b12-c926-490f-a0f6-837c99e84fb0@linux.ibm.com \
--to=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=meissner@linux.ibm.com \
--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).