GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Zhangjin Wu <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: [PATCH nolibc 0/19] Updates to nolibc for v6.7 (and three for v6.6)
Date: Fri, 27 Oct 2023 02:09:17 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 4666 bytes --]

[out-of-tree]

[ Sorry, please ignore the last one with lwt.eu, it should be 1wt.eu, seems a typo:
https://lore.kernel.org/lkml/b34ce3cf-3fcc-4eb0-a658-229c197455ef@paulmck-laptop/ ]

Hi, Paul, Thomas and Willy

I just learned our nolibc tree has been moved to another git repo and
have seen this PR series. I was waiting for a new branch in Willy's repo ;-)

Just a question: seems some patches of mine have been queued to Willy's
local repo, but I haven't seen in this PR, I can't remember which ones
are queued exactly, here may be at least one of them:

https://lore.kernel.org/linux-kselftest/[email protected]/

Or do I need to send a new series for them? some of the commit message issues
have been changed by Willy manually, so, that series online can not be merged
simply, If necessary, I'm ok to resend them.

BR,
Zhangjin

> Hello!
> 
> This series contains nolibc updates, with the first three (1-3) being
> urgent for v6.6 and the remainder (4-19) being for the upcoming v6.7
> merge window.
> 
> 1.	tools/nolibc: i386: Fix a stack misalign bug on _start, courtesy
> 	of Ammar Faizi.
> 
> 2.	MAINTAINERS: nolibc: update tree location, courtesy of Thomas
> 	Weißschuh.
> 
> 3.	tools/nolibc: mark start_c as weak, courtesy of Thomas Weißschuh.
> 
> 4.	tools/nolibc: add stdarg.h header, courtesy of Thomas Weißschuh.
> 
> 5.	selftests/nolibc: use -nostdinc for nolibc-test, courtesy of
> 	Thomas Weißschuh.
> 
> 6.	tools/nolibc: x86-64: Use `rep movsb` for `memcpy()` and
> 	`memmove()`, courtesy of Ammar Faizi.
> 
> 7.	tools/nolibc: x86-64: Use `rep stosb` for `memset()`, courtesy
> 	of Ammar Faizi.
> 
> 8.	tools/nolibc: string: Remove the `_nolibc_memcpy_down()` function,
> 	courtesy of Ammar Faizi.
> 
> 9.	tools/nolibc: string: Remove the `_nolibc_memcpy_up()` function,
> 	courtesy of Ammar Faizi.
> 
> 10.	selftests/nolibc: libc-test: avoid -Wstringop-overflow warnings,
> 	courtesy of Thomas Weißschuh.
> 
> 11.	selftests/nolibc: don't embed initramfs into kernel image,
> 	courtesy of Thomas Weißschuh.
> 
> 12.	selftests/nolibc: allow building i386 with multiarch compiler,
> 	courtesy of Thomas Weißschuh.
> 
> 13.	tools/nolibc: avoid unused parameter warnings for ENOSYS
> 	fallbacks, courtesy of Thomas Weißschuh.
> 
> 14.	tools/nolibc: don't define new syscall number, courtesy of
> 	Thomas Weißschuh.
> 
> 15.	tools/nolibc: automatically detect necessity to use pselect6,
> 	courtesy of Thomas Weißschuh.
> 
> 16.	tools/nolibc: drop test for getauxval(AT_PAGESZ), courtesy of
> 	Thomas Weißschuh.
> 
> 17.	tools/nolibc: add support for constructors and destructors,
> 	courtesy of Thomas Weißschuh.
> 
> 18.	selftests/nolibc: use qemu-system-ppc64 for ppc64le, courtesy
> 	of Thomas Weißschuh.
> 
> 19.	selftests/nolibc: add tests for multi-object linkage, courtesy
> 	of Thomas Weißschuh.
> 
> 						Thanx, Paul
> 
> ------------------------------------------------------------------------
> 
>  b/MAINTAINERS                                          |    2 
>  b/tools/include/nolibc/Makefile                        |    1 
>  b/tools/include/nolibc/arch-aarch64.h                  |    3 
>  b/tools/include/nolibc/arch-i386.h                     |    4 -
>  b/tools/include/nolibc/arch-loongarch.h                |    4 -
>  b/tools/include/nolibc/arch-riscv.h                    |    3 
>  b/tools/include/nolibc/arch-x86_64.h                   |   29 ++++++++
>  b/tools/include/nolibc/crt.h                           |    1 
>  b/tools/include/nolibc/nolibc.h                        |    4 -
>  b/tools/include/nolibc/stdarg.h                        |   16 ++++
>  b/tools/include/nolibc/stdio.h                         |    3 
>  b/tools/include/nolibc/string.h                        |    4 +
>  b/tools/include/nolibc/sys.h                           |    2 
>  b/tools/testing/selftests/nolibc/.gitignore            |    1 
>  b/tools/testing/selftests/nolibc/Makefile              |    2 
>  b/tools/testing/selftests/nolibc/nolibc-test-linkage.c |   26 +++++++
>  b/tools/testing/selftests/nolibc/nolibc-test-linkage.h |    9 ++
>  b/tools/testing/selftests/nolibc/nolibc-test.c         |    6 -
>  tools/include/nolibc/arch-x86_64.h                     |   13 +++
>  tools/include/nolibc/crt.h                             |   23 ++++++
>  tools/include/nolibc/string.h                          |   32 ++------
>  tools/include/nolibc/sys.h                             |   61 +++++++++--------
>  tools/testing/selftests/nolibc/Makefile                |   57 +++++++++------
>  tools/testing/selftests/nolibc/nolibc-test.c           |   22 +++++-
>  24 files changed, 234 insertions(+), 94 deletions(-)

             reply	other threads:[~2023-10-26 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 18:09 Zhangjin Wu [this message]
2023-10-27  8:21 ` [PATCH nolibc 0/19] Updates to nolibc for v6.7 (and three for v6.6) Willy Tarreau
  -- strict thread matches above, loose matches on Subject: below --
2023-10-26 18:05 Zhangjin Wu
2023-10-27  2:16 ` Paul E. McKenney
2023-10-12 19:32 Paul E. McKenney

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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