From: caiyinyu <caiyinyu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, libc-alpha@sourceware.org
Cc: adhemerval.zanella@linaro.org,
"Chenghua Xu" <xuchenghua@loongson.cn>,
王洪虎 <wanghonghu@loongson.cn>,
lixing@loongson.cn
Subject: Re: [PATCH] LoongArch: Modify some member names in mcontext_t and ucontext_t structs to align them with the kernel.
Date: Mon, 3 Apr 2023 10:52:42 +0800 [thread overview]
Message-ID: <0268b8f7-f918-f36b-fd01-5ddbb1b0a23b@loongson.cn> (raw)
In-Reply-To: <bef2bfeb-8905-cf19-5f17-cefd8ea9787b@loongson.cn>
Gentle ping.
The previous patch was missing a line of code: #undef __ctx. Here's the
updated patch:
https://sourceware.org/pipermail/libc-alpha/2023-April/146859.html
在 2023/3/31 上午11:52, caiyinyu 写道:
>
> 在 2023/3/24 下午3:40, Xi Ruoyao 写道:
>> On Fri, 2023-03-24 at 14:25 +0800, caiyinyu wrote:
>>> typedef struct mcontext_t
>>> {
>>> - unsigned long long __pc;
>>> - unsigned long long __gregs[32];
>>> - unsigned int __flags;
>>> - unsigned long long __extcontext[0] __attribute__((__aligned__(16)));
>>> + unsigned long long __ctx(sc_pc);
>>> + unsigned long long __ctx(sc_regs)[32];
>>> + unsigned int __ctx(sc_flags);
>>> + unsigned long long __ctx(sc_extcontext)[0]
>>> __attribute__((__aligned__(16)));
>>> } mcontext_t;
>> How about this?
>>
>> __extension__ typedef struct mcontext_t
>> {
>> union
>> {
>> /* Backward compatibility names. */
>> struct
>> {
>> unsigned long long __pc;
>> unsigned long long __gregs[32];
>> unsigned int __flags;
>> unsigned long long __extcontext[0] __attribute__((__aligned__(16)));
>> };
>> struct
>> {
>> unsigned long long __ctx(sc_pc);
>> unsigned long long __ctx(sc_regs)[32];
>> unsigned int __ctx(sc_flags);
>> unsigned long long __ctx(sc_extcontext)[0]
>> __attribute__((__aligned__(16)));
>> };
>> };
>> } mcontext_t;
>
> Your plan caused fails in glibc conform tests.
>
> We wanted to inform you that we are aware that the proposed
> modification[1] will affect the public API. However, since LoongArch
> Musl has not yet been released, and the LoongArch Euler system, Debian
> system, Alpine, and other systems are still in early development
> stages, we have not yet widely released the system. Therefore, we
> believe it is necessary to proceed with the modification.
>
> We do not want to carry the burden of history and remain committed to
> proceeding with the modification. Additionally, we also plan to
> backport this patch[1] to versions 2.36 and 2.37 to address the issue
> of inconsistent naming of musl/glibc/kernel sigcontext/mcontext_t
> members from the source, resolving this issue at the root. This will
> eliminate potential problems for future software and system development.
>
> [1] patch:
>
> https://sourceware.org/pipermail/libc-alpha/2023-March/146607.html
>
next prev parent reply other threads:[~2023-04-03 2:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 6:25 caiyinyu
2023-03-24 7:00 ` Xi Ruoyao
2023-03-24 7:40 ` Xi Ruoyao
2023-03-31 3:52 ` caiyinyu
2023-04-03 2:52 ` caiyinyu [this message]
2023-04-03 8:56 ` Xi Ruoyao
2023-04-03 9:18 ` caiyinyu
2023-04-03 9:25 ` Xi Ruoyao
2023-04-03 9:41 ` caiyinyu
2023-04-03 10:12 ` Xi Ruoyao
2023-04-03 10:45 ` caiyinyu
2023-04-03 12:03 ` caiyinyu
2023-04-03 2:51 caiyinyu
2023-04-03 12:29 ` Adhemerval Zanella Netto
2023-04-03 12:33 ` caiyinyu
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=0268b8f7-f918-f36b-fd01-5ddbb1b0a23b@loongson.cn \
--to=caiyinyu@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=lixing@loongson.cn \
--cc=wanghonghu@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).