public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc@gcc.gnu.org, Wang Xuerui <i@xen0n.name>
Subject: Re: Number of ALU in la464.md
Date: Tue, 27 Sep 2022 10:40:29 +0800	[thread overview]
Message-ID: <29636360-2958-faaf-35ff-ed5d9b757900@loongson.cn> (raw)
In-Reply-To: <85ef5c4398d48c7e1c87692c5f2d56a755f19c09.camel@xry111.site>

You are right, I just added it before, but I didn't see the performance 
improvement,

so I didn't change this place.

在 2022/9/25 下午7:28, Xi Ruoyao 写道:
> Hi,
>
> According to the schematic
> (https://loongson.github.io/LoongArch-Documentation/Loongson-3A5000-usermanual-EN.html#la464-processor-core,
> Figure 5) we have 4 ALUs in LA464, but in la464.md we only define
> la464_alu1 and la464_alu2.
>
> Should we add la464_alu{3,4} as well, or am I missing something here?


  reply	other threads:[~2022-09-27  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 11:28 Xi Ruoyao
2022-09-27  2:40 ` Lulu Cheng [this message]
2022-09-27  2:50   ` Xi Ruoyao

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=29636360-2958-faaf-35ff-ed5d9b757900@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=xry111@xry111.site \
    /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).