All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	Marco Crivellari <marco.crivellari@suse.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [linux-next:master 5904/8679] <instantiation>:7:11: error: expected an immediate
Date: Thu, 8 May 2025 21:53:27 +0200	[thread overview]
Message-ID: <aB0Lt7e4tnRK355u@alpha.franken.de> (raw)
In-Reply-To: <20250508164308.GC834338@ax162>

On Thu, May 08, 2025 at 05:43:08PM +0100, Nathan Chancellor wrote:
> On Wed, May 07, 2025 at 01:49:02PM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   0a00723f4c2d0b273edd0737f236f103164a08eb
> > commit: 56651128e2fbad80f632f388d6bf1f39c928267a [5904/8679] MIPS: Fix idle VS timer enqueue
> > config: mips-gpr_defconfig (https://download.01.org/0day-ci/archive/20250507/202505071331.Z0N2eSkr-lkp@intel.com/config)
> > compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071331.Z0N2eSkr-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/202505071331.Z0N2eSkr-lkp@intel.com/
> > 
> > All errors (new ones prefixed by >>):
> > 
> > >> <instantiation>:7:11: error: expected an immediate
> >     ori $26, r4k_wait_idle_size - 2
> >              ^
> >    <instantiation>:10:13: error: expected an immediate
> >     addiu $26, r4k_wait_exit - r4k_wait_insn + 2
> >                ^
> >    <instantiation>:10:29: error: expected an immediate
> >     addiu $26, r4k_wait_exit - r4k_wait_insn + 2
> >                                ^
> > >> <instantiation>:7:11: error: expected an immediate
> >     ori $26, r4k_wait_idle_size - 2
> >              ^
> >    <instantiation>:10:13: error: expected an immediate
> >     addiu $26, r4k_wait_exit - r4k_wait_insn + 2
> >                ^
> >    <instantiation>:10:29: error: expected an immediate
> >     addiu $26, r4k_wait_exit - r4k_wait_insn + 2
> >                                ^
> 
> I do not see this with tip of tree LLVM. It seems this was only recently
> supported in the integrated assembler:
> 
> https://github.com/llvm/llvm-project/commit/b65e0947cade9bd39036a7700b54c1df4ec00756

cool

> If it is not easy to work around, we can probably just leave it broken
> and tell anybody who notices to upgrade their compiler.

I wrapped my head around it today, but no idea how to solve it...

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2025-05-08 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  5:49 [linux-next:master 5904/8679] <instantiation>:7:11: error: expected an immediate kernel test robot
2025-05-08 16:43 ` Nathan Chancellor
2025-05-08 19:53   ` Thomas Bogendoerfer [this message]
2025-05-12 10:47     ` Maciej W. Rozycki
2025-05-21 22:44       ` Nathan Chancellor

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=aB0Lt7e4tnRK355u@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=macro@orcam.me.uk \
    --cc=marco.crivellari@suse.com \
    --cc=nathan@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.