Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [arm-integrator:b4/arm-generic-entry-v6.14-rc1-cleanup-patch 33/33] arch/arm/kernel/entry-common.S:200:2: error: invalid instruction, any one of the following would fix this:
Date: Fri, 7 Mar 2025 20:06:35 +0800	[thread overview]
Message-ID: <202503072001.bAYqc08h-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git b4/arm-generic-entry-v6.14-rc1-cleanup-patch
head:   231c6ca98693dab095d461ce8d7bfdbf73b0f7e0
commit: 231c6ca98693dab095d461ce8d7bfdbf73b0f7e0 [33/33] ARM: entry: Straighten syscall returns
config: arm-randconfig-003-20250307 (https://download.01.org/0day-ci/archive/20250307/202503072001.bAYqc08h-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503072001.bAYqc08h-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/202503072001.bAYqc08h-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/arm/kernel/entry-common.S:200:2: error: invalid instruction, any one of the following would fix this:
    b 9002
    ^
   arch/arm/kernel/entry-common.S:200:4: note: invalid operand for instruction
    b 9002
      ^
   arch/arm/kernel/entry-common.S:200:2: note: instruction requires: thumb
    b 9002
    ^


vim +200 arch/arm/kernel/entry-common.S

   166	
   167		/* saved_psr and saved_pc are now dead */
   168	
   169		uaccess_disable tbl
   170		get_thread_info tsk
   171		/* Save a per-task copy of SP for sigreturn */
   172		str	sp, [tsk, #TI_SP_SYSCALL]
   173	
   174		adr	tbl, sys_call_table		@ load syscall table pointer
   175	
   176	#if defined(CONFIG_OABI_COMPAT)
   177		/*
   178		 * If the swi argument is zero, this is an EABI call and we do nothing.
   179		 *
   180		 * If this is an old ABI call, get the syscall number into scno and
   181		 * get the old ABI syscall table address.
   182		 */
   183		bics	r10, r10, #0xff000000
   184		strne	r10, [tsk, #TI_ABI_SYSCALL]
   185		streq	scno, [tsk, #TI_ABI_SYSCALL]
   186		eorne	scno, r10, #__NR_OABI_SYSCALL_BASE
   187		ldrne	tbl, =sys_oabi_call_table
   188	#elif !defined(CONFIG_AEABI)
   189		bic	scno, scno, #0xff000000		@ mask off SWI op-code
   190		str	scno, [tsk, #TI_ABI_SYSCALL]
   191		eor	scno, scno, #__NR_SYSCALL_BASE	@ check OS number
   192	#else
   193		str	scno, [tsk, #TI_ABI_SYSCALL]
   194	#endif
   195		mov	r1, sp				@ put regs into r1
   196		stmdb	sp!, {r4, r5}			@ push fifth and sixth args
   197		mov	r0, tbl
   198		mov	r2, scno			@ syscall number from r7
   199		bl	invoke_syscall
 > 200		b	9002
   201	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-03-07 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202503072001.bAYqc08h-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=llvm@lists.linux.dev \
    --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