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

On Tue, 2022-09-27 at 10:40 +0800, Lulu Cheng wrote:
> You are right, I just added it before, but I didn't see the performance 
> improvement,
> 
> so I didn't change this place.

Alright, so just left la464.md as-is for now.

I'll try Phoronix bench suite on LoongArch once a binary distro is in a
good shape (Phoronix bench suite uses package managers like apt or dnf
but they are not in Linux From Scratch, and I don't have access to
expensive SPEC CPU suite).

> 在 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?
> 

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2022-09-27  2:51 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
2022-09-27  2:50   ` Xi Ruoyao [this message]

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=ef128d7b73fadf694902f3626187ebd5667c5e99.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=chenglulu@loongson.cn \
    --cc=gcc@gcc.gnu.org \
    --cc=i@xen0n.name \
    /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).