From: Lehua Ding <lehua.ding@rivai.ai>
To: Peter Bergner <bergner@linux.ibm.com>, gcc-patches@gcc.gnu.org
Cc: vmakarov@redhat.com, richard.sandiford@arm.com,
juzhe.zhong@rivai.ai,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH V3 0/7] ira/lra: Support subreg coalesce
Date: Wed, 15 Nov 2023 11:12:48 +0800 [thread overview]
Message-ID: <C81219CED2A6F26F+bbd1db81-a694-4c9e-9a6e-f052794a57da@rivai.ai> (raw)
In-Reply-To: <12de2836-f68d-4a13-91f2-fdc9dd888ac0@linux.ibm.com>
On 2023/11/15 7:22, Peter Bergner wrote:
> On 11/12/23 6:08 AM, Lehua Ding wrote:
>> V3 Changes:
>> 1. fix three ICE.
>> 2. rebase
>
>
> I tested this on powerpc64le-linux and powerpc64-linux. The LE build
> bootstrapped fine and it looks like only one testsuite FAIL which I have
> to look into why it's FAILing.
>
> The BE build did bootstrap, but the 32-bit and 64-bit testsuite runs both
> had lots of FAILs (over 100 between them both) which I have yet to look
> into what is happening.
I've applied for machine permissions on the compile farm, can you give
me the way to compile and run tests on PPC64BE machine? I'll take a look
at it too, thanks a lot.
> I'll also note I have done no performance testing yet until I have an
> idea of what the testsuite failures are. I think a patch like this that
> can affect the performance of all architectures needs some performance
> testing to ensure we don't have unintended performance degradations.
> I'll have someone on my team kick off some builds once I have a handle
> on the testsuite FAILs.
This is really great, thanks for helping to test the performance.
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
next prev parent reply other threads:[~2023-11-15 3:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 12:08 Lehua Ding
2023-11-12 12:08 ` [PATCH V3 1/7] df: Add DF_LIVE_SUBREG problem Lehua Ding
2023-11-13 22:38 ` Vladimir Makarov
2023-11-14 8:14 ` Richard Biener
2023-11-14 8:38 ` Lehua Ding
2023-11-14 9:03 ` Richard Biener
2023-11-14 14:52 ` Vladimir Makarov
2023-11-14 17:18 ` Vladimir Makarov
2023-11-14 18:29 ` Vladimir Makarov
2023-11-20 20:11 ` Richard Sandiford
2023-11-21 6:35 ` Lehua Ding
2023-11-12 12:08 ` [PATCH V3 2/7] ira: Switch to live_subreg data Lehua Ding
2023-11-14 20:26 ` Vladimir Makarov
2023-11-12 12:08 ` [PATCH V3 3/7] ira: Support subreg live range track Lehua Ding
2023-11-14 20:37 ` Vladimir Makarov
2023-11-12 12:08 ` [PATCH V3 4/7] ira: Support subreg copy Lehua Ding
2023-11-16 21:13 ` Vladimir Makarov
2023-11-17 2:06 ` Lehua Ding
2023-11-17 14:05 ` Vladimir Makarov
2023-11-18 8:00 ` Lehua Ding
2023-11-18 8:06 ` Sam James
2023-11-18 8:16 ` Lehua Ding
2023-11-18 8:24 ` Sam James
2023-11-18 8:27 ` Lehua Ding
2023-11-12 12:08 ` [PATCH V3 5/7] ira: Add all nregs >= 2 pseudos to tracke subreg list Lehua Ding
2023-11-16 21:14 ` Vladimir Makarov
2023-11-12 12:08 ` [PATCH V3 6/7] lra: Switch to live_subreg data flow Lehua Ding
2023-11-12 12:08 ` [PATCH V3 7/7] lra: Support subreg live range track and conflict detect Lehua Ding
2023-11-13 16:43 ` [PATCH V3 0/7] ira/lra: Support subreg coalesce Dimitar Dimitrov
2023-11-15 2:10 ` Lehua Ding
2023-11-13 19:37 ` Vladimir Makarov
2023-11-14 5:37 ` Lehua Ding
2023-11-14 23:33 ` Peter Bergner
2023-11-14 23:22 ` Peter Bergner
2023-11-15 3:12 ` Lehua Ding [this message]
2023-11-15 3:33 ` Peter Bergner
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=C81219CED2A6F26F+bbd1db81-a694-4c9e-9a6e-f052794a57da@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.org \
--cc=vmakarov@redhat.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).