public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: WANG Xuerui <i@xen0n.name>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Lulu Cheng <chenglulu@loongson.cn>, Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: [PATCH] LoongArch: Set 4 * (issue rate) as the default for -falign-functions and -falign-loops
Date: Tue, 18 Apr 2023 20:39:49 +0800	[thread overview]
Message-ID: <2957dad7-a211-06b8-168c-8649c508c399@xen0n.name> (raw)
In-Reply-To: <20230418121753.50830-1-xry111@xry111.site>

Hi,

Thanks for helping confirming on GCC and porting this! I'd never know 
even GCC lacked this adaptation without someone actually checking... Too 
many things are taken for granted these days.

On 2023/4/18 20:17, Xi Ruoyao wrote:
> According to Xuerui's LLVM changeset [1], doing so can make a
> significant performace gain.
>
> Bootstrapped and regtested on loongarch64-linux-gnu.  Ok for GCC 14?
>
> [1]:https://reviews.llvm.org/D148622
>
> gcc/ChangeLog:
>
> 	* config/loongarch/loongarch.cc
> 	(loongarch_option_override_internal): If -falign-functions is
> 	used but the alignment is not explicitly specified, set it to
> 	4 * loongarch_issue_rate ().  Likewise for -falign-loops.
> ---
>   gcc/config/loongarch/loongarch.cc | 11 +++++++++++
>   1 file changed, 11 insertions(+)
>
> diff --git a/gcc/config/loongarch/loongarch.cc b/gcc/config/loongarch/loongarch.cc
> index 06fc1cd0604..6552484de7c 100644
> --- a/gcc/config/loongarch/loongarch.cc
> +++ b/gcc/config/loongarch/loongarch.cc
> @@ -6236,6 +6236,17 @@ loongarch_option_override_internal (struct gcc_options *opts)
>         && !opts->x_optimize_size)
>       opts->x_flag_prefetch_loop_arrays = 1;
>   
> +  /* Align functions and loops to (issue rate) * (insn size) to improve
> +     the throughput of the fetching units.  */
What about gating all of these on !opts->x_optimize_size, similar to 
what aarch64 does?
> +  char *align = XNEWVEC (char, 16);
> +  sprintf (align, "%d", loongarch_issue_rate () * 4);
> +
> +  if (opts->x_flag_align_functions && !opts->x_str_align_functions)
> +    opts->x_str_align_functions = align;
> +
> +  if (opts->x_flag_align_loops && !opts->x_str_align_loops)
> +    opts->x_str_align_loops = align;
> +
>     if (TARGET_DIRECT_EXTERN_ACCESS && flag_shlib)
>       error ("%qs cannot be used for compiling a shared library",
>   	   "-mdirect-extern-access");
Otherwise LGTM, thanks!

  reply	other threads:[~2023-04-18 12:39 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 [this message]
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
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=2957dad7-a211-06b8-168c-8649c508c399@xen0n.name \
    --to=i@xen0n.name \
    --cc=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=xry111@xry111.site \
    --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).