From: Florian Weimer <fweimer@redhat.com>
To: caiyinyu <caiyinyu@loongson.cn>
Cc: libc-alpha@sourceware.org, xuchenghua@loongson.cn,
joseph_myers@mentor.com
Subject: Re: [PATCH v3 00/13] GLIBC LoongArch PATCHES
Date: Tue, 10 May 2022 21:37:34 +0200 [thread overview]
Message-ID: <8735hhb2m9.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220509022611.1248063-1-caiyinyu@loongson.cn> (caiyinyu@loongson.cn's message of "Mon, 9 May 2022 10:25:58 +0800")
> GCC and Binutils Loongarch parts have been into GNU Open Source community.
> Loongarch kernal may be no problem on 5.19:
It seems that the Linux 5.19 release date could be really close to the
glibc 2.36 release date, or even after it. I think we wouldn't want to
release with an ABI whose kernel interface is not in a mainline kernel
yet.
We have the option to backdate ABIs, so we could release the port with a
GLIBC_2.36 ABI baseline in glibc 2.37.
Or we could merge the port now, and back it out once more if Linux 5.19
does not get released in time.
Maybe it's sufficient if the Linux port makes it to mainline during the
5.19 rc phase?
Thoughts?
Thanks,
Florian
next prev parent reply other threads:[~2022-05-10 19:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 2:25 caiyinyu
2022-05-09 2:25 ` [PATCH v4 01/13] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-05-11 17:05 ` Adhemerval Zanella
2022-05-09 2:26 ` [PATCH v4 02/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-05-09 2:26 ` [PATCH v4 03/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-05-09 2:26 ` [PATCH v4 04/13] LoongArch: ABI Implementation caiyinyu
2022-05-09 2:26 ` [PATCH v4 05/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-05-09 2:26 ` [PATCH v4 06/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-05-09 2:26 ` [PATCH v4 07/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-05-09 2:26 ` [PATCH v4 08/13] LoongArch: Linux Syscall Interface caiyinyu
2022-05-11 7:02 ` Arnd Bergmann
2022-05-11 13:20 ` Adhemerval Zanella
2022-05-15 7:53 ` caiyinyu
2022-05-16 18:44 ` Adhemerval Zanella
2022-05-09 2:26 ` [PATCH v4 09/13] LoongArch: Linux ABI caiyinyu
2022-05-11 7:08 ` Arnd Bergmann
2022-05-11 13:27 ` Adhemerval Zanella
2022-05-11 17:32 ` Joseph Myers
2022-05-15 3:32 ` caiyinyu
2022-05-16 18:49 ` Adhemerval Zanella
2022-05-18 3:40 ` caiyinyu
2022-05-18 7:33 ` Arnd Bergmann
2022-05-09 2:26 ` [PATCH v4 10/13] LoongArch: Add ABI Lists caiyinyu
2022-05-10 19:37 ` Florian Weimer [this message]
2022-05-10 20:33 ` [PATCH v3 00/13] GLIBC LoongArch PATCHES Joseph Myers
2022-05-11 6:57 ` Arnd Bergmann
2022-05-11 13:17 ` Adhemerval Zanella
-- strict thread matches above, loose matches on Subject: below --
2022-04-15 1:31 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=8735hhb2m9.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=caiyinyu@loongson.cn \
--cc=joseph_myers@mentor.com \
--cc=libc-alpha@sourceware.org \
--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).