From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Quentin Monnet" <qmo@kernel.org>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
"Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2 0/2] tools/build: Fix s390(x) cross-compilation with clang
Date: Wed, 2 Jul 2025 14:41:33 -0700 [thread overview]
Message-ID: <20250702214133.GB2103156@ax162> (raw)
In-Reply-To: <20250620-tools-cross-s390-v2-0-ecda886e00e5@linutronix.de>
On Fri, Jun 20, 2025 at 01:00:26PM +0200, Thomas Weißschuh wrote:
> The heuristic to derive a clang target triple from a GCC one does not work
> for s390. GCC uses "s390-linux" while clang expects "s390x-linux" or
> "powerz-linux".
This generally seems fine to me but I do not interact with tools/ much.
> There doesn't seem to be a formal maintainer for this file.
> Maybe the clang/llvm maintainers can pick it up.
I do not have a tree nor do I send pull requests to Linus. Perhaps you
could just pick this up in the nolibc tree or have Shuah take it as a
greater kselftests update?
Cheers,
Nathan
next prev parent reply other threads:[~2025-07-02 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 11:00 Thomas Weißschuh
2025-06-20 11:00 ` [PATCH v2 1/2] " Thomas Weißschuh
2025-06-20 11:00 ` [PATCH v2 2/2] tools/nolibc: drop s390 clang target override Thomas Weißschuh
2025-07-02 21:41 ` Nathan Chancellor [this message]
2025-07-04 11:41 ` [PATCH v2 0/2] tools/build: Fix s390(x) cross-compilation with clang 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=20250702214133.GB2103156@ax162 \
--to=nathan@kernel.org \
--cc=andrii@kernel.org \
--cc=jean-philippe@linaro.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=qmo@kernel.org \
--cc=thomas.weissschuh@linutronix.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
all inboxes | Powered by JetHome®