From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Daniel Palmer <daniel@0x0f.com>
Cc: w@1wt.eu, linux-m68k@lists.linux-m68k.org, geert@linux-m68k.org,
linux-kernel@vger.kernel.org, Daniel Palmer <daniel@thingy.jp>
Subject: Re: [PATCH v2] tools/nolibc: Add m68k support
Date: Sat, 26 Apr 2025 18:01:49 +0200 [thread overview]
Message-ID: <dcbd27d0-eb72-447c-8bfd-810a6939b0dd@t-8ch.de> (raw)
In-Reply-To: <20250426065323.259267-1-daniel@0x0f.com>
Hi!
On 2025-04-26 15:53:23+0900, Daniel Palmer wrote:
> From: Daniel Palmer <daniel@thingy.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@thingy.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>
prev parent reply other threads:[~2025-04-26 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 6:53 Daniel Palmer
2025-04-26 16:01 ` Thomas Weißschuh [this message]
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=dcbd27d0-eb72-447c-8bfd-810a6939b0dd@t-8ch.de \
--to=linux@weissschuh.net \
--cc=daniel@0x0f.com \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®