From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0'
Date: Tue, 11 Aug 2026 03:47:02 +0800 [thread overview]
Message-ID: <202608110230.c32X9KXj-lkp@intel.com> (raw)
Hi Huacai,
FYI, the error/warning still remains.
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'
loongarch64-linux-gcc: note: valid arguments to '-march=' are: abi-default la464 la64v1.0 la64v1.1 la664 loongarch64 native; did you mean 'la64v1.0'?
loongarch64-linux-gcc: error: unrecognized argument in option '-mabi=ilp32s'
loongarch64-linux-gcc: note: valid arguments to '-mabi=' are: lp64d lp64f lp64s
>> loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0'
loongarch64-linux-gcc: note: valid arguments to '-march=' are: abi-default la464 la64v1.0 la64v1.1 la664 loongarch64 native; did you mean 'la64v1.0'?
loongarch64-linux-gcc: error: unrecognized argument in option '-mabi=ilp32s'
loongarch64-linux-gcc: note: valid arguments to '-mabi=' are: lp64d lp64f lp64s
make[3]: *** [scripts/Makefile.build:289: scripts/mod/empty.o] Error 1 shuffle=28659922
>> loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0'
loongarch64-linux-gcc: note: valid arguments to '-march=' are: abi-default la464 la64v1.0 la64v1.1 la664 loongarch64 native; did you mean 'la64v1.0'?
loongarch64-linux-gcc: error: unrecognized argument in option '-mabi=ilp32s'
loongarch64-linux-gcc: note: valid arguments to '-mabi=' are: lp64d lp64f lp64s
make[3]: *** [scripts/Makefile.build:184: scripts/mod/devicetable-offsets.s] Error 1 shuffle=28659922
make[3]: Target 'scripts/mod/' not remade because of errors.
make[2]: *** [Makefile:1336: prepare0] Error 2 shuffle=28659922
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2 shuffle=28659922
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2 shuffle=28659922
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-10 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 19:47 kernel test robot [this message]
2026-08-10 20:01 ` loongarch64-linux-gcc: error: unrecognized argument in option '-march=la32v1.0' Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
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=202608110230.c32X9KXj-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.