From: Nathan Chancellor <nathan@kernel.org>
To: WANG Rui <wangrui@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, loongson-kernel@lists.loongnix.cn,
Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH] scripts/min-tool-version.sh: Raise min clang version to 18.0.0 for loongarch
Date: Mon, 8 Jan 2024 09:37:59 -0700 [thread overview]
Message-ID: <20240108163759.GA2899468@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20240108033138.217032-1-wangrui@loongson.cn>
On Mon, Jan 08, 2024 at 11:31:38AM +0800, WANG Rui wrote:
> The existing mainline clang development version encounters diffculties
> compiling the LoongArch kernel module. It is anticipated that this issue
> will be resolved in the upcoming 18.0.0 release. To prevent user
> confusion arising from broken builds, it is advisable to raise the
> minimum required clang version for LoongArch to 18.0.0.
>
> Suggested-by: Nathan Chancellor <nathan@kernel.org>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> Signed-off-by: WANG Rui <wangrui@loongson.cn>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Thanks a lot for all the work driving getting everything to work
properly with LLVM!
> ---
> scripts/min-tool-version.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/min-tool-version.sh b/scripts/min-tool-version.sh
> index c62066825f53..9faa4d3d91e3 100755
> --- a/scripts/min-tool-version.sh
> +++ b/scripts/min-tool-version.sh
> @@ -26,6 +26,8 @@ gcc)
> llvm)
> if [ "$SRCARCH" = s390 ]; then
> echo 15.0.0
> + elif [ "$SRCARCH" = loongarch ]; then
> + echo 18.0.0
> else
> echo 11.0.0
> fi
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-01-08 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 3:31 WANG Rui
2024-01-08 16:31 ` Nick Desaulniers
2024-01-08 16:37 ` Nathan Chancellor [this message]
2024-01-09 1:40 ` Huacai Chen
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=20240108163759.GA2899468@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=wangrui@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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®