public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Guo Ren <guoren@linux.alibaba.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@rivosinc.com>
Subject: [ammarfaizi2-block:palmer/linux/riscv-compat 13/20] arch/riscv/kernel/process.c:102:35: error: use of undeclared identifier 'SR_UXL'
Date: Tue, 8 Mar 2022 20:13:30 +0800	[thread overview]
Message-ID: <202203082040.sCWBscgE-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block palmer/linux/riscv-compat
head:   ab7e33a6b819f009c3c9ccf69b2f44c1ad84a5a0
commit: d463ff83f0d26ce352a0969c86a9accf70d30977 [13/20] riscv: compat: process: Add UXL_32 support in start_thread
config: riscv-randconfig-r005-20220308 (https://download.01.org/0day-ci/archive/20220308/202203082040.sCWBscgE-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e)
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
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/ammarfaizi2/linux-block/commit/d463ff83f0d26ce352a0969c86a9accf70d30977
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block palmer/linux/riscv-compat
        git checkout d463ff83f0d26ce352a0969c86a9accf70d30977
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash

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:101:6: error: implicit declaration of function 'is_compat_task' [-Werror,-Wimplicit-function-declaration]
           if (is_compat_task())
               ^
>> arch/riscv/kernel/process.c:102:35: error: use of undeclared identifier 'SR_UXL'
                   regs->status = (regs->status & ~SR_UXL) | SR_UXL_32;
                                                   ^
>> arch/riscv/kernel/process.c:102:45: error: use of undeclared identifier 'SR_UXL_32'
                   regs->status = (regs->status & ~SR_UXL) | SR_UXL_32;
                                                             ^
   arch/riscv/kernel/process.c:104:35: error: use of undeclared identifier 'SR_UXL'
                   regs->status = (regs->status & ~SR_UXL) | SR_UXL_64;
                                                   ^
>> arch/riscv/kernel/process.c:104:45: error: use of undeclared identifier 'SR_UXL_64'
                   regs->status = (regs->status & ~SR_UXL) | SR_UXL_64;
                                                             ^
   5 errors generated.


vim +/SR_UXL +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-03-08 12:14 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=202203082040.sCWBscgE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=guoren@linux.alibaba.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=palmer@rivosinc.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