llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [hnaz-mm:master 175/188] ld.lld: error: arch/riscv/built-in.a(kernel/perf_regs.o):(function perf_reg_value: .text+0x58): relocation R_RISCV_HI20 out of range: 531169 is not in [-524288, 524287]; references perf_reg_value.__if_trace.6.1
Date: Sun, 10 Apr 2022 05:58:06 +0800	[thread overview]
Message-ID: <202204100540.6fgSEvWS-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
TO: Jonathan Lassoff <jof@thejof.com>
CC: Johannes Weiner <hannes@cmpxchg.org>
CC: Petr Mladek <pmladek@suse.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>

tree:   https://github.com/hnaz/linux-mm master
head:   71e0d841ccd1c91e7038d385825e26342e87d198
commit: 5d611fa3457866c49ee52a993eb44fa230f25cf1 [175/188] fatfs: add FAT messages to printk index
config: riscv-randconfig-r016-20220410 (https://download.01.org/0day-ci/archive/20220410/202204100540.6fgSEvWS-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 256c6b0ba14e8a7ab6373b61b7193ea8c0a3651c)
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/hnaz/linux-mm/commit/5d611fa3457866c49ee52a993eb44fa230f25cf1
        git remote add hnaz-mm https://github.com/hnaz/linux-mm
        git fetch --no-tags hnaz-mm master
        git checkout 5d611fa3457866c49ee52a993eb44fa230f25cf1
        # 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>

Note: the hnaz-mm/master HEAD 71e0d841ccd1c91e7038d385825e26342e87d198 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

>> ld.lld: error: arch/riscv/built-in.a(kernel/perf_regs.o):(function perf_reg_value: .text+0x58): relocation R_RISCV_HI20 out of range: 531169 is not in [-524288, 524287]; references perf_reg_value.__if_trace.6.1
   >>> referenced by perf_regs.c
   >>> defined in arch/riscv/built-in.a(kernel/perf_regs.o)
--
>> ld.lld: error: arch/riscv/built-in.a(kernel/perf_regs.o):(function perf_reg_value: .text+0x84): relocation R_RISCV_HI20 out of range: 530978 is not in [-524288, 524287]; references perf_reg_value.______f.8
   >>> referenced by perf_regs.c
   >>> defined in arch/riscv/built-in.a(kernel/perf_regs.o)

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for DRM_GEM_SHMEM_HELPER
   Depends on HAS_IOMEM && DRM && MMU
   Selected by
   - DRM_SSD130X && HAS_IOMEM && DRM

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-09 21:58 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=202204100540.6fgSEvWS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@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;
as well as URLs for NNTP newsgroup(s).