From: caiyinyu <caiyinyu@loongson.cn>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
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 20:33:43 +0800 [thread overview]
Message-ID: <5575a4f7-00f6-9006-7a56-52b4c2a7401b@loongson.cn> (raw)
In-Reply-To: <5c13bb4b-0e9f-5f46-3955-a651f5f34ec6@linaro.org>
在 2023/4/3 下午8:29, Adhemerval Zanella Netto 写道:
>
> On 02/04/23 23:51, caiyinyu wrote:
>> During the construction of the LoongArch Alpine system,
>> we found that there is an inconsistency in the member
>> names of mcontext_t and ucontext_t between musl and glibc,
>> which can cause compilation errors. After testing, we have
>> decided to modify some member names.
>>
>> This patch will be backported to glibc versions 2.36 and 2.37.
> You can't do it without breaking the API and I don't think we should allow
> the precedence. Afaik loongarch is not yet on musl, so why can't you mimic
> what loongarch already defined in glibc on musl?
The latest patch:
https://sourceware.org/pipermail/libc-alpha/2023-April/146897.html
The latest emails:
https://sourceware.org/pipermail/libc-alpha/2023-April/thread.html (bottom)
next prev parent reply other threads:[~2023-04-03 12:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 2:51 caiyinyu
2023-04-03 12:29 ` Adhemerval Zanella Netto
2023-04-03 12:33 ` caiyinyu [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=5575a4f7-00f6-9006-7a56-52b4c2a7401b@loongson.cn \
--to=caiyinyu@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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).