The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	kernel test robot <lkp@intel.com>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: error: ABI 'o32' is not supported on CPU 'mips64'
Date: Fri, 6 Sep 2024 11:42:34 +0800	[thread overview]
Message-ID: <Ztp6Khar6h3T4RSI@rli9-mobl> (raw)
In-Reply-To: <f661ed7e-5d69-403c-bfc8-7581eb8a6e76@app.fastmail.com>

On Thu, Sep 05, 2024 at 10:56:15AM +0100, Jiaxun Yang wrote:
> 
> 
> 在2024年9月5日九月 上午10:22,Maciej W. Rozycki写道:
> > On Sat, 31 Aug 2024, kernel test robot wrote:
> >
> >> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >> head:   fb24560f31f9dff2c97707cfed6029bfebebaf1c
> >> commit: 2326c8f2022636a1e47402ffd09a3b28f737275f MIPS: Fix fallback march for SB1
> >> date:   7 weeks ago
> >> config: mips-randconfig-r121-20240830 (https://download.01.org/0day-ci/archive/20240831/202408310705.y2OPq3Xs-lkp@intel.com/config)
> >> compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
> >> reproduce: (https://download.01.org/0day-ci/archive/20240831/202408310705.y2OPq3Xs-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
> >> | Reported-by: kernel test robot <lkp@intel.com>
> >> | Closes: https://lore.kernel.org/oe-kbuild-all/202408310705.y2OPq3Xs-lkp@intel.com/
> >> 
> >> All errors (new ones prefixed by >>):
> >> 
> >> >> error: ABI 'o32' is not supported on CPU 'mips64'
> >> >> error: error: ABI 'o32' is not supported on CPU 'mips64'
> >>    ABI 'o32' is not supported on CPU 'mips64'
> >>    make[3]: *** [scripts/Makefile.build:117: scripts/mod/devicetable-offsets.s] Error 1
> >>    make[3]: *** [scripts/Makefile.build:244: scripts/mod/empty.o] Error 1
> >>    make[3]: Target 'scripts/mod/' not remade because of errors.
> >>    make[2]: *** [Makefile:1207: prepare0] Error 2
> >>    make[2]: Target 'prepare' not remade because of errors.
> >>    make[1]: *** [Makefile:240: __sub-make] Error 2
> >>    make[1]: Target 'prepare' not remade because of errors.
> >>    make: *** [Makefile:240: __sub-make] Error 2
> >>    make: Target 'prepare' not remade because of errors.
> >
> >  This is a compiler bug.  The MIPS64 ISA does certainly support the o32 
> > ABI, so they need to fix their "CPU 'mips64'" definition.
> 
> Just for record, this has been fixed in LLVM-17 [1], while the bit is still
> on LLVM 15.

Thanks for the info, the bot will ignore the issue on clang-15/16 in future.

> 
> Thanks
> [1]: https://github.com/llvm/llvm-project/commit/7983f8aca82e258174849f1cc6a70029353e9887
> 
> >
> >   Maciej
> 
> -- 
> - Jiaxun
> 

      reply	other threads:[~2024-09-06  3:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 23:42 error: ABI 'o32' is not supported on CPU 'mips64' kernel test robot
2024-09-05  9:22 ` Maciej W. Rozycki
2024-09-05  9:56   ` Jiaxun Yang
2024-09-06  3:42     ` Philip Li [this message]

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=Ztp6Khar6h3T4RSI@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=macro@orcam.me.uk \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tsbogend@alpha.franken.de \
    /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