[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dcbd27d0-eb72-447c-8bfd-810a6939b0dd@t-8ch.de>
Date: Sat, 26 Apr 2025 18:01:49 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Daniel Palmer <daniel@...f.com>
Cc: w@....eu, linux-m68k@...ts.linux-m68k.org, geert@...ux-m68k.org,
linux-kernel@...r.kernel.org, Daniel Palmer <daniel@...ngy.jp>
Subject: Re: [PATCH v2] tools/nolibc: Add m68k support
Hi!
On 2025-04-26 15:53:23+0900, Daniel Palmer wrote:
> From: Daniel Palmer <daniel@...ngy.jp>
>
> Add nolibc support for m68k. Should be helpful for nommu where
> linking libc can bloat even hello world to the point where you get
> an OOM just trying to load it.
Thanks for the patch, it does look good in general.
Could you rebase it onto the nolibc next branch [0] for easier application?
Also normal clang does not support m68k yet, so it should be skipped in
run-tests.sh in the llvm case.
As for mmu vs nommu, this choice has no impact on the userspace
application itself, right? If so, having only one configuration in the
nolibc testsuite should be enough.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git/log/?h=next
>
> Signed-off-by: Daniel Palmer <daniel@...ngy.jp>
> ---
> tools/include/nolibc/arch-m68k.h | 141 ++++++++++++++++++++
> tools/include/nolibc/arch.h | 2 +
> tools/testing/selftests/nolibc/Makefile | 5 +
> tools/testing/selftests/nolibc/run-tests.sh | 1 +
> 4 files changed, 149 insertions(+)
> create mode 100644 tools/include/nolibc/arch-m68k.h
<snip>
Powered by blists - more mailing lists