All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Guo Ren <guoren@linux.alibaba.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [csky-linux:riscv_compat_v6 13/20] arch/riscv/kernel/process.c:102:49: error: 'SR_UXL' undeclared; did you mean 'SR_XS'?
Date: Thu, 24 Feb 2022 23:30:20 +0800	[thread overview]
Message-ID: <202202242354.qbKyVs40-lkp@intel.com> (raw)

tree:   https://github.com/c-sky/csky-linux riscv_compat_v6
head:   4aafa1859382d5a159bdafe2956453feafd38845
commit: 4cebbf9e791522be5b6e7cea289ab1c43c66cbc0 [13/20] riscv: compat: process: Add UXL_32 support in start_thread
config: riscv-buildonly-randconfig-r006-20220224 (https://download.01.org/0day-ci/archive/20220224/202202242354.qbKyVs40-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/c-sky/csky-linux/commit/4cebbf9e791522be5b6e7cea289ab1c43c66cbc0
        git remote add csky-linux https://github.com/c-sky/csky-linux
        git fetch --no-tags csky-linux riscv_compat_v6
        git checkout 4cebbf9e791522be5b6e7cea289ab1c43c66cbc0
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/riscv/kernel/process.c: In function 'start_thread':
   arch/riscv/kernel/process.c:101:13: error: implicit declaration of function 'is_compat_task' [-Werror=implicit-function-declaration]
     101 |         if (is_compat_task())
         |             ^~~~~~~~~~~~~~
>> arch/riscv/kernel/process.c:102:49: error: 'SR_UXL' undeclared (first use in this function); did you mean 'SR_XS'?
     102 |                 regs->status = (regs->status & ~SR_UXL) | SR_UXL_32;
         |                                                 ^~~~~~
         |                                                 SR_XS
   arch/riscv/kernel/process.c:102:49: note: each undeclared identifier is reported only once for each function it appears in
>> arch/riscv/kernel/process.c:102:59: error: 'SR_UXL_32' undeclared (first use in this function)
     102 |                 regs->status = (regs->status & ~SR_UXL) | SR_UXL_32;
         |                                                           ^~~~~~~~~
>> arch/riscv/kernel/process.c:104:59: error: 'SR_UXL_64' undeclared (first use in this function)
     104 |                 regs->status = (regs->status & ~SR_UXL) | SR_UXL_64;
         |                                                           ^~~~~~~~~
   cc1: some warnings being treated as errors


vim +102 arch/riscv/kernel/process.c

    85	
    86	void start_thread(struct pt_regs *regs, unsigned long pc,
    87		unsigned long sp)
    88	{
    89		regs->status = SR_PIE;
    90		if (has_fpu()) {
    91			regs->status |= SR_FS_INITIAL;
    92			/*
    93			 * Restore the initial value to the FP register
    94			 * before starting the user program.
    95			 */
    96			fstate_restore(current, regs);
    97		}
    98		regs->epc = pc;
    99		regs->sp = sp;
   100	
   101		if (is_compat_task())
 > 102			regs->status = (regs->status & ~SR_UXL) | SR_UXL_32;
   103		else
 > 104			regs->status = (regs->status & ~SR_UXL) | SR_UXL_64;
   105	}
   106	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

                 reply	other threads:[~2022-02-24 15:30 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=202202242354.qbKyVs40-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=guoren@linux.alibaba.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.