From: Feiyang Chen <chris.chenfeiyang@gmail.com>
To: mengqinggang <mengqinggang@loongson.cn>
Cc: Feiyang Chen <chenfeiyang@loongson.cn>,
liuzhensong@loongson.cn, xuchenghua@loongson.cn,
chenhuacai@loongson.cn, binutils@sourceware.org
Subject: Re: [PATCH] LoongArch: Add fcsr register names support
Date: Wed, 14 Jun 2023 15:28:37 +0800 [thread overview]
Message-ID: <CACWXhK=aDDv2hzXjqhXtHqqaMrgpUj4o6XgwPtzCyd=9BqGNGQ@mail.gmail.com> (raw)
In-Reply-To: <e96c94d0-fc8c-0cb5-9178-94b6b7a6be4f@loongson.cn>
On Wed, Jun 14, 2023 at 3:07 PM mengqinggang <mengqinggang@loongson.cn> wrote:
>
> Because there are only fcsr0-fcsr3, whether fc_htab just append r0-r3?
>
> Any general register bigger than r3 is invalid?
>
I believe this is a good approach, similar to what LLVM appears to do.
However, I'm not certain if there might be some code intentionally
using r4, as the manual doesn't explicitly forbid its usage, only
stating that doing so would result in undefined outcomes.
>
> 在 2023/6/12 下午4:36, Feiyang Chen 写道:
> > + /* Add general purpose registers for backward compatibility. */
> > + for (i = 0; i < ARRAY_SIZE (loongarch_r_normal_name); i++)
> > + str_hash_insert (fc_htab, loongarch_r_normal_name[i], (void *) (i + 1),
> > + 0);
>
next prev parent reply other threads:[~2023-06-14 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 8:36 Feiyang Chen
2023-06-13 1:05 ` Chenghua Xu
2023-06-13 9:49 ` WANG Xuerui
2023-06-14 4:27 ` Feiyang Chen
2023-06-16 9:20 ` WANG Xuerui
2023-06-16 9:30 ` Xi Ruoyao
2023-06-14 3:33 ` mengqinggang
2023-06-14 4:14 ` Feiyang Chen
2023-06-14 7:07 ` mengqinggang
2023-06-14 7:28 ` Feiyang Chen [this message]
2023-06-14 8:39 ` mengqinggang
2023-06-14 9:27 ` Feiyang Chen
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='CACWXhK=aDDv2hzXjqhXtHqqaMrgpUj4o6XgwPtzCyd=9BqGNGQ@mail.gmail.com' \
--to=chris.chenfeiyang@gmail.com \
--cc=binutils@sourceware.org \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@loongson.cn \
--cc=liuzhensong@loongson.cn \
--cc=mengqinggang@loongson.cn \
--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).