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 v2 2/4] parisc: Makefile: use the regular compiler to build a native 32-bit vDSO
Date: Wed, 8 Apr 2026 23:00:33 +0200 [thread overview]
Message-ID: <40bb6110-abfb-4d6c-8682-8933ad0b6816@t-8ch.de> (raw)
In-Reply-To: <bcf93eb6-3937-4165-a4cd-569d1cef8f7e@gmx.de>
On 2026-04-08 22:52:22+0200, Helge Deller wrote:
> On 4/8/26 21:42, Thomas Weißschuh wrote:
> > On 2026-04-08 21:01:45+0200, Helge Deller wrote:
> > > On 4/8/26 20:18, 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.
> > >
> > > I'm not sure, but still I think this logic of your patches #1 and #2
> > > may break the builds for others.
> > > That said, I'd prefer if we can get it working without your patches #1 and #2.
> > > Can't we do without them?
> >
> > They are mostly do avoid hacks in the nolibc testsuite.
> > I'll drop them and use this instead: ---
> > a/tools/testing/selftests/nolibc/run-tests.sh
> > +++ b/tools/testing/selftests/nolibc/run-tests.sh
> > @@ -175,6 +175,10 @@ test_arch() {
> > fi
> > MAKE=(make -f Makefile.nolibc -j"${nproc}" XARCH="${arch}" CROSS_COMPILE="${cross_compile}" LLVM="${llvm}" O="${build_dir}")
> > + if [ "$arch" = "parisc32" ]; then
> > + MAKE+=("CROSS32CC=${cross_compile}gcc")
> can you try if
> MAKE += " ARCH=parisc"
> works too?
Makefile.nolibc will already build the kernel with ARCH based on XARCH.
> > However in the long-term it would be nice not the need it anymore.
> > Afaik is parisc the only architecture which needs a special compiler
> > specification for the native vDSO.
>
> actually it doesn't. It will figure out itself.
Thanks!
> > > I tried your patch series, but they fail to apply to my series or
> > > upstream.
> >
> > These patches are currently based on nolibc/for-next
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git/log/?h=for-next
>
> Ok.
Do you want to review the nolibc bits?
If so I will wait for your review.
Thomas
next prev parent reply other threads:[~2026-04-08 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 18:18 [PATCH v2 0/4] tools/nolibc: add support for 32-bit parisc Thomas Weißschuh
2026-04-08 18:18 ` [PATCH v2 1/4] parisc: Makefile: move CROSS_COMPILE detection before CROSS32CC one Thomas Weißschuh
2026-04-08 18:18 ` [PATCH v2 2/4] parisc: Makefile: use the regular compiler to build a native 32-bit vDSO Thomas Weißschuh
2026-04-08 19:01 ` Helge Deller
2026-04-08 19:42 ` Thomas Weißschuh
2026-04-08 20:52 ` Helge Deller
2026-04-08 21:00 ` Thomas Weißschuh [this message]
2026-04-08 18:18 ` [PATCH v2 3/4] selftests/nolibc: avoid function pointer comparisons Thomas Weißschuh
2026-04-08 18:18 ` [PATCH v2 4/4] tools/nolibc: add support for 32-bit parisc 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=40bb6110-abfb-4d6c-8682-8933ad0b6816@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®