public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: WANG Xuerui <i.swmail@xen0n.name>
Cc: Fangrui Song <maskray@google.com>,  Alan Modra <amodra@gmail.com>,
	libc-alpha <libc-alpha@sourceware.org>,
	 caiyinyu <caiyinyu@loongson.cn>,
	liuzhensong <liuzhensong@loongson.cn>,
	 binutils@sourceware.org
Subject: Re: glibc 2.36 - Slushy freeze (3 weeks to release)
Date: Tue, 12 Jul 2022 09:33:12 +0200	[thread overview]
Message-ID: <87a69evl8n.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ada40d73-6b93-da19-a23c-de35ee3315a0@xen0n.name> (WANG Xuerui's message of "Tue, 12 Jul 2022 14:42:23 +0800")

* WANG Xuerui:

> All is not lost, though, as the LoongArch "new world" (the fully
> community-driven openly developed ABI we're currently all working on,
> as opposed to the stopgap MIPS-esque ABI Loongson initially shipped in 
> commercial products) is nowhere near popular, at least in the 1~1.5
> years to come; and we as distribution packages already educate the 
> current "seed" users of new-world LoongArch to expect to update or
> re-install as often as possible to stay on the bleeding edge. So IMO 
> fixing the linker and sunsetting R_LARCH_NONE support in glibc loader
> could be feasible after all, just it won't be a quick process.

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.

Thanks,
Florian


  reply	other threads:[~2022-07-12  7:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 15:20 Carlos O'Donell
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 [this message]
2022-07-12  8:49               ` Xi Ruoyao
2022-07-12  8:58                 ` Florian Weimer
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
2022-07-11 20:23 ` Noah Goldstein

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=87a69evl8n.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=maskray@google.com \
    /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).