mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
	"Huacai Chen" <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>
Subject: Re: loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0'
Date: Mon, 10 Aug 2026 22:01:14 +0200	[thread overview]
Message-ID: <25b2a242-9a28-42fe-a361-477f4298617f@app.fastmail.com> (raw)
In-Reply-To: <202608110230.c32X9KXj-lkp@intel.com>

On Mon, Aug 10, 2026, at 21:47, kernel test robot wrote:
>
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> master
> head:   06cf61899d6498b33e4b7c87d99d5bd471ccc375
> commit: 3d9aba6618d115750729bba2d1f8af180bd7d3bd LoongArch: Adjust 
> build infrastructure for 32BIT/64BIT
> date:   4 months ago
> config: loongarch-randconfig-001-20260811 
> (https://download.01.org/0day-ci/archive/20260811/202608110230.c32X9KXj-lkp@intel.com/config)
> compiler: loongarch64-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): 
> (https://download.01.org/0day-ci/archive/20260811/202608110230.c32X9KXj-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new 
> version of
> the same patch/commit), kindly add following tags
> | Fixes: 3d9aba6618d1 ("LoongArch: Adjust build infrastructure for 
> 32BIT/64BIT")
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: 
> https://lore.kernel.org/oe-kbuild-all/202608110230.c32X9KXj-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0'

I see that this option is supported by gcc-16 but not gcc-15.
Clang-22 also doesn't have it, not sure about clang-23 or higher.

How about this change?

--- a/arch/loongarch/Kconfig
+++ b/arch/loongarch/Kconfig
@@ -224,6 +224,7 @@ choice
 
 config 32BIT
        bool "32-bit kernel"
+       depends on GCC_VERSION >= 160000 || CLANG_VERSION >= 230000
        help
          Select this option if you want to build a 32-bit kernel.
 

  reply	other threads:[~2026-08-10 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 19:47 kernel test robot
2026-08-10 20:01 ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-22  1:25 kernel test robot
2026-04-29 21:46 kernel test robot

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=25b2a242-9a28-42fe-a361-477f4298617f@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=chenhuacai@loongson.cn \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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®