From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: WANG Xuerui <i@xen0n.name>,
Youling Tang <tangyouling@loongson.cn>,
Chenghua Xu <xuchenghua@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Jinyang He <hejinyang@loongson.cn>
Subject: Re: 回复:[PATCH v5] LoongArch: add movable attribute
Date: Tue, 9 Aug 2022 21:03:38 +0800 [thread overview]
Message-ID: <afcf5b09-f0c0-c83f-6240-b4024a9a72d9@loongson.cn> (raw)
In-Reply-To: <6393bd75250c1cb46377b7eee4afd7db4bda7e25.camel@xry111.site>
在 2022/8/9 下午7:30, Xi Ruoyao 写道:
> Sorry for late reply, I'm rebuilding my entire Linux system (from
> scratch) for Glibc-2.36 and Binutils-2.39 update and I just reached the
> mail client.
>
> On Mon, 2022-08-08 at 12:53 +0800, Lulu Cheng wrote:
>> I still think it makes a little bit more sense to put attribute(model)
>> and -mcmodel together.
>>
>> -mcmodel sets the access range of all symbols in a single fileand
>> attribute (model) sets the
>>
>> accsess range of a single symbol in a file. For example
>> __attribute__((model(normal/large/extreme))).
> It might make sense, but then it would not be what we want for per-CPU
> symbols. What we want here is "treat a local symbol as-if it's global",
> while each code model may already treat local symbol and global symbol
> differently.
>
> Disambiguation: here "local" means "defined in this TU", "global"
> otherwise (not "local variable" in C).
>
> I'll send v6 with the name "addr_global" if no objection.
>
I am implementing the mode of cmodel=extreme. In this mode, the value of
the relative offset is a signed 64-bit value, so this can solve the
access problem of the variables of the kernel precpu.
So I wonder if it is necessary to add another attribute like addr_global?
next prev parent reply other threads:[~2022-08-09 13:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 14:22 [PATCH] LoongArch: add addr_global attribute Xi Ruoyao
2022-07-29 15:31 ` [PATCH v2] " Xi Ruoyao
2022-07-29 17:17 ` [PATCH v3] " Xi Ruoyao
2022-07-30 3:13 ` Lulu Cheng
2022-07-30 6:03 ` Huacai Chen
2022-07-31 9:05 ` Chenghua Xu
2022-08-01 10:04 ` [PATCH v4] LoongArch: add movable attribute Xi Ruoyao
2022-08-01 10:07 ` [PATCH v5] " Xi Ruoyao
2022-08-03 1:36 ` Xi Ruoyao
2022-08-03 2:59 ` WANG Xuerui
2022-08-03 3:15 ` Xi Ruoyao
[not found] ` <-2muj1c-68saz6jhkcyw3jo1xp-1mgcvnkbqi2wjp6tue-qsso54-emxgu3-k85590-kpgox7-w67u6h3cai1l-5bi887dsgzsu-g4d7i7-wl316qxrucx4kv4on7-mnna36-iremg8-nwc5ot-9041t2-hu8nsl.1659495047941@email.android.com>
2022-08-03 3:10 ` 回复:[PATCH " Xi Ruoyao
2022-08-04 7:47 ` Xi Ruoyao
2022-08-05 1:05 ` Lulu Cheng
2022-08-05 1:28 ` Xi Ruoyao
2022-08-05 2:38 ` Lulu Cheng
2022-08-05 2:51 ` Xi Ruoyao
2022-08-05 3:34 ` Xi Ruoyao
2022-08-05 3:45 ` Xi Ruoyao
2022-08-05 4:01 ` Lulu Cheng
2022-08-05 6:03 ` Xi Ruoyao
2022-08-05 7:19 ` Lulu Cheng
2022-08-05 7:41 ` WANG Xuerui
2022-08-05 7:58 ` Lulu Cheng
2022-08-05 9:53 ` Xi Ruoyao
2022-08-08 4:53 ` Lulu Cheng
2022-08-09 11:30 ` Xi Ruoyao
2022-08-09 13:03 ` Lulu Cheng [this message]
2022-08-09 14:04 ` 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=afcf5b09-f0c0-c83f-6240-b4024a9a72d9@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hejinyang@loongson.cn \
--cc=i@xen0n.name \
--cc=tangyouling@loongson.cn \
--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).