From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Helge Deller <deller@gmx.de>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH 1/3] parisc: Makefile: use the regular compiler to build a native 32-bit vDSO
Date: Tue, 7 Apr 2026 20:06:27 +0200 [thread overview]
Message-ID: <76ccb417-822f-4fcc-bf8a-f829f8a14ff4@t-8ch.de> (raw)
In-Reply-To: <b0eaa2ff-cf5e-4508-be41-61d265943b6a@gmx.de>
Hi Helge,
On 2026-04-07 19:14:23+0200, Helge Deller wrote:
> On 4/7/26 18:37, Thomas Weißschuh wrote:
> > When building a native 32-bit kernel $(CC) the compiler is obviously
> > able to compile 32-bit code. There is no need to force the user to
> > configure a dedicated 32-bit compiler.
> >
> > Use the regular compiler for the 32-bit vDSO when it is sufficient.
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
>
> This part is quite fragile, especially since the kernel is often also
> cross built...
I also used this patch during cross-building and it worked so far.
> I can add the series to for-next branch of the parisc git tree to see if this
> breaks somewhere. (unless you take care of it at another git tree?)
I'd like to take the nolibc patches through the nolibc tree.
If you want to take the Makefile patch through your tree into the v7.1
merge window that would also work, as I will only apply these patches
for the next v7.2 cycle.
Thomas
next prev parent reply other threads:[~2026-04-07 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 16:37 [PATCH 0/3] tools/nolibc: add support for 32-bit parisc Thomas Weißschuh
2026-04-07 16:37 ` [PATCH 1/3] parisc: Makefile: use the regular compiler to build a native 32-bit vDSO Thomas Weißschuh
2026-04-07 17:14 ` Helge Deller
2026-04-07 18:06 ` Thomas Weißschuh [this message]
2026-04-07 19:27 ` Helge Deller
2026-04-07 20:20 ` Helge Deller
2026-04-07 21:27 ` Thomas Weißschuh
2026-04-07 22:33 ` Helge Deller
2026-04-07 16:37 ` [PATCH 2/3] selftests/nolibc: avoid function pointer comparisons Thomas Weißschuh
2026-04-07 17:20 ` Helge Deller
2026-04-07 18:11 ` Thomas Weißschuh
2026-04-07 16:37 ` [PATCH 3/3] tools/nolibc: add support for 32-bit parisc Thomas Weißschuh
2026-04-07 17:33 ` Helge Deller
2026-04-07 18:14 ` Thomas Weißschuh
2026-04-07 18:40 ` Helge Deller
2026-04-07 18:50 ` Thomas Weißschuh
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=76ccb417-822f-4fcc-bf8a-f829f8a14ff4@t-8ch.de \
--to=linux@weissschuh.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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®