mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Garg, Shivank" <shivankg@amd.com>
To: kernel test robot <lkp@intel.com>,
	chenhuacai@kernel.org, kernel@xen0n.name
Cc: oe-kbuild-all@lists.linux.dev,
	Sean Christopherson <seanjc@google.com>,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [linux-next:master 2198/11041] arch/loongarch/kernel/switch.S:28:18: error: operand must be a symbol with modifier (e.g. %pc_lo12) or an integer in the range
Date: Mon, 24 Nov 2025 11:23:26 +0530	[thread overview]
Message-ID: <30d886b1-510b-4d65-a3bb-8c49a1c4a3a4@amd.com> (raw)
In-Reply-To: <202511240656.0NaPcJs1-lkp@intel.com>



On 11/24/2025 4:27 AM, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   d724c6f85e80a23ed46b7ebc6e38b527c09d64f5
> commit: f634f10809ec3d51d9529dfb0f99bc7cec1b5eff [2198/11041] mm/mempolicy: Export memory policy symbols
> config: loongarch-randconfig-r051-20251123 (https://download.01.org/0day-ci/archive/20251124/202511240656.0NaPcJs1-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/20251124/202511240656.0NaPcJs1-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/202511240656.0NaPcJs1-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>>> arch/loongarch/kernel/switch.S:28:18: error: operand must be a symbol with modifier (e.g. %pc_lo12) or an integer in the range [-2048, 2047]
>     ld.d $r20, $r5, 3808
>                     ^
> 
> 
> vim +28 arch/loongarch/kernel/switch.S
> 
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  12  
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  13  /*
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  14   * task_struct *__switch_to(task_struct *prev, task_struct *next,
> 613d4164f5a503 Huacai Chen 2025-01-25  15   *			    struct thread_info *next_ti, void *sched_ra, void *sched_cfa)
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  16   */
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  17  	.align	5
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  18  SYM_FUNC_START(__switch_to)
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  19  	csrrd	t1, LOONGARCH_CSR_PRMD
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  20  	stptr.d	t1, a0, THREAD_CSRPRMD
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  21  
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  22  	cpu_save_nonscratch a0
> 803b0fc5c3f2ba Huacai Chen 2022-05-31  23  	stptr.d	ra, a0, THREAD_REG01
> 93a4fa622eb061 Qing Zhang  2022-08-06  24  	stptr.d a3, a0, THREAD_SCHED_RA
> 93a4fa622eb061 Qing Zhang  2022-08-06  25  	stptr.d a4, a0, THREAD_SCHED_CFA
> 09f33601bf940f Huacai Chen 2022-12-10  26  #if defined(CONFIG_STACKPROTECTOR) && !defined(CONFIG_SMP)
> 09f33601bf940f Huacai Chen 2022-12-10  27  	la	t7, __stack_chk_guard
> 09f33601bf940f Huacai Chen 2022-12-10 @28  	LONG_L	t8, a1, TASK_STACK_CANARY
> 
> :::::: The code at line 28 was first introduced by commit
> :::::: 09f33601bf940f955c10a6e75a1c1b7bcadee5e2 LoongArch: Add basic STACKPROTECTOR support
> 
> :::::: TO: Huacai Chen <chenhuacai@loongson.cn>
> :::::: CC: Huacai Chen <chenhuacai@loongson.cn>
> 
Hi,

This appears unrelated to the commit and looks like LoongArch assembly issue.

CC: LoongArch maintainers.

Thanks,
Shivank

           reply	other threads:[~2025-11-24  5:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <202511240656.0NaPcJs1-lkp@intel.com>]

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=30d886b1-510b-4d65-a3bb-8c49a1c4a3a4@amd.com \
    --to=shivankg@amd.com \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=loongarch@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=seanjc@google.com \
    /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®