From: Florian Weimer <fweimer@redhat.com>
To: Xi Ruoyao via Libc-alpha <libc-alpha@sourceware.org>
Cc: WANG Xuerui <i.swmail@xen0n.name>,
Xi Ruoyao <xry111@xry111.site>,
binutils@sourceware.org, Alan Modra <amodra@gmail.com>,
liuzhensong <liuzhensong@loongson.cn>,
caiyinyu <caiyinyu@loongson.cn>
Subject: Re: glibc 2.36 - Slushy freeze (3 weeks to release)
Date: Tue, 12 Jul 2022 10:58:29 +0200 [thread overview]
Message-ID: <87wnciu2q2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <fead68f629f5eafc841457479aeaa7b77be3b3ca.camel@xry111.site> (Xi Ruoyao via Libc-alpha's message of "Tue, 12 Jul 2022 16:49:10 +0800")
* Xi Ruoyao via Libc-alpha:
> On Tue, 2022-07-12 at 09:33 +0200, Florian Weimer via Libc-alpha wrote:
>
>> Does it really make sense to add a glibc port now if we are going to
>> switch to a different ABI two or three releases from now? I don't
>> think
>> so.
>
> The Glibc patches under review (and the upstreamed kernel/gcc/binutils
> code) are already using the new ABI.
>
> The "old" ABI was only used by commercial distros for customers who want
> to use LoongArch platforms before all the open source components are
> reviewed and upstreamed properly. Old ABI will never be a part of
> upstream code.
>
> Once glibc is upstreamed we will consider the ABI stabilized, and start
> to encourage people to use upstreamed ABI. (Obviously we can't do it
> now: we can't just tell people to "rebuild everything per month".)
Okay, that clarifies that aspect, and addresses my concerns. Thanks.
Florian
next prev parent reply other threads:[~2022-07-12 8:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fef8c3c7-fd30-d8b5-e539-f0f21d562c51@redhat.com>
2022-07-11 16:06 ` Xi Ruoyao
2022-07-11 19:10 ` Adhemerval Zanella Netto
2022-07-12 0:48 ` Xi Ruoyao
2022-07-12 1:02 ` Xi Ruoyao
2022-07-12 2:32 ` Alan Modra
2022-07-12 4:24 ` Fangrui Song
2022-07-12 6:19 ` Jan Beulich
2022-07-12 6:42 ` WANG Xuerui
2022-07-12 7:33 ` Florian Weimer
2022-07-12 8:49 ` Xi Ruoyao
2022-07-12 8:58 ` Florian Weimer [this message]
2022-07-12 9:24 ` Xi Ruoyao
2022-07-12 10:21 ` Adhemerval Zanella Netto
2022-07-12 11:01 ` Adhemerval Zanella Netto
2022-07-12 12:15 ` Michael Matz
2022-07-12 13:17 ` Florian Weimer
2022-07-12 13:28 ` Michael Matz
2022-07-15 22:34 ` Hans-Peter Nilsson
2022-07-12 12:48 ` caiyinyu
2022-07-12 13:00 ` Xi Ruoyao
2022-07-12 7:33 ` Andrew Waterman
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=87wnciu2q2.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=caiyinyu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=libc-alpha@sourceware.org \
--cc=liuzhensong@loongson.cn \
--cc=xry111@xry111.site \
/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).