From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 0/4] tools/nolibc: MIPS: entrypoint cleanups and N32/N64 ABIs
Date: Sun, 30 Mar 2025 21:19:23 +0200 [thread overview]
Message-ID: <20250330191923.M_4QMXqa@breakpoint.cc> (raw)
In-Reply-To: <7fef431b-1b68-4967-8f8a-d2b49e403578@t-8ch.de>
On 2025-03-29 10:51:47 [+0100], Thomas Weißschuh wrote:
>
> Does the following work for you when running kust "make nolibc-test"?
I had to manually apply this on top of b4/nolibc-mips-n32. The resulting
make produced the native 64bit binary.
Sebastian
prev parent reply other threads:[~2025-03-30 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 17:02 [PATCH v2 0/4] tools/nolibc: MIPS: entrypoint cleanups and N32/N64 ABIs Thomas Weißschuh
2025-02-25 17:02 ` [PATCH v2 1/4] tools/nolibc: MIPS: drop $gp setup Thomas Weißschuh
2025-02-25 17:02 ` [PATCH v2 2/4] tools/nolibc: MIPS: drop manual stack pointer alignment Thomas Weißschuh
2025-02-25 17:02 ` [PATCH v2 3/4] tools/nolibc: MIPS: drop noreorder option Thomas Weißschuh
2025-02-25 17:02 ` [PATCH v2 4/4] tools/nolibc: MIPS: add support for N64 and N32 ABIs Thomas Weißschuh
2025-03-01 11:21 ` [PATCH v2 0/4] tools/nolibc: MIPS: entrypoint cleanups and N32/N64 ABIs Willy Tarreau
2025-03-01 15:47 ` Maciej W. Rozycki
2025-03-01 15:52 ` Thomas Weißschuh
2025-03-01 16:23 ` Willy Tarreau
2025-03-26 20:54 ` Sebastian Andrzej Siewior
2025-03-26 21:51 ` Thomas Weißschuh
2025-03-26 22:04 ` Sebastian Andrzej Siewior
2025-03-29 9:51 ` Thomas Weißschuh
2025-03-30 19:19 ` Sebastian Andrzej Siewior [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=20250330191923.M_4QMXqa@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=macro@orcam.me.uk \
--cc=shuah@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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;
as well as URLs for NNTP newsgroup(s).