From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: WANG Xuerui <i@xen0n.name>, Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: [PATCH] LoongArch: Set 4 * (issue rate) as the default for -falign-functions and -falign-loops
Date: Mon, 12 Jun 2023 17:19:39 +0800 [thread overview]
Message-ID: <d1bc5a65e81dcaaabd071f94ddd81ead312323e2.camel@xry111.site> (raw)
In-Reply-To: <45202d67-5272-3dfb-e5bb-6318b28bab0f@loongson.cn>
On Tue, 2023-05-30 at 09:30 +0800, Lulu Cheng wrote:
>
> 在 2023/5/29 下午2:09, Xi Ruoyao 写道:
> > On Tue, 2023-04-18 at 21:06 +0800, Lulu Cheng wrote:
> > > Hi, ruoyao:
> > >
> > > Thank you so much for making this submission. But we are testing
> > > the
> > > impact of these two alignment parameters
> > >
> > > (also including -falign-jumps and -falign-lables ) on performance.
> > > So
> > > before the result comes out, this patch will
> > >
> > > not be merged into the main branch for the time being.
> > Hi!
> >
> > Is there an estimate when the benchmark will be done? If it will be
> > done soon I'll wait for the result before performing a full system
> > rebuild, otherwise I'll use my gut feeling to specify a -falign-
> > functions= value for the build :).
> >
> Sorry for taking so long to reply to the email. From our current test
> results,
>
> the performance of the SPEC is best when combined with -falign-
> loops=16,
>
> -falign-jumps=16, -falign-functions=32 and -falign-lables=16.
I've completed a system rebuild with -falign-
{jumps,functions,labels}=16. I've missed -falign-loops=16 but the doc
says -falign-labels=16 implies -falign-jumps=16 and -falign-loops=16 (if
-falign-jumps or -falign-loops are not set explicitly with a larger
value).
I'll make a patch to set -falign-functions=32 and -falign-labels=16 with
-mtune={la464,loongarch64} after setting a basic develop environment on
the new system... And I'm wondering if things will change with LA664
:).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-06-12 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 12:17 Xi Ruoyao
2023-04-18 12:39 ` WANG Xuerui
2023-04-18 12:45 ` Xi Ruoyao
2023-04-18 12:51 ` WANG Xuerui
2023-04-18 13:00 ` Xi Ruoyao
2023-04-18 13:06 ` Lulu Cheng
2023-04-18 13:16 ` Xi Ruoyao
2023-05-29 6:09 ` Xi Ruoyao
2023-05-30 1:30 ` Lulu Cheng
2023-06-12 9:19 ` Xi Ruoyao [this message]
2023-06-13 2:20 ` Lulu Cheng
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=d1bc5a65e81dcaaabd071f94ddd81ead312323e2.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xuchenghua@loongson.cn \
/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).