From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: kernel test robot <lkp@intel.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [linux-next:master 14270/15002] ld.lld: error: init/built-in.a(initramfs.o):(function wait_for_initramfs: .text+0x24): relocation R_RISCV_HI20 out of range: 530109 is not in [-524288, 524287]; references initramfs_cookie
Date: Sun, 3 Apr 2022 09:40:49 +0000 [thread overview]
Message-ID: <d403df3f-4277-7800-b583-94bdbd7aa9c5@csgroup.eu> (raw)
In-Reply-To: <202204030606.gML0qvDb-lkp@intel.com>
Le 03/04/2022 à 00:08, kernel test robot a écrit :
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: e5071887cd2296a7704dbcd10c1cedf0f11cdbd5
> commit: af41d2866f7d75bbb38d487f6ec7770425d70e45 [14270/15002] powerpc/64: Fix build failure with allyesconfig in book3s_64_entry.S
> config: riscv-randconfig-r022-20220403 (https://download.01.org/0day-ci/archive/20220403/202204030606.gML0qvDb-lkp@intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c4a1b07d0979e7ff20d7d541af666d822d66b566)
> 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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=af41d2866f7d75bbb38d487f6ec7770425d70e45
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout af41d2866f7d75bbb38d487f6ec7770425d70e45
> # 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>
I can't understand how a change in assembly in POWERPC would impact a
RISCV build.
There must be something wrong with the robot.
Christophe
>
> All errors (new ones prefixed by >>):
>
>>> ld.lld: error: init/built-in.a(initramfs.o):(function wait_for_initramfs: .text+0x24): relocation R_RISCV_HI20 out of range: 530109 is not in [-524288, 524287]; references initramfs_cookie
> >>> referenced by initramfs.c
> >>> defined in init/built-in.a(initramfs.o)
> --
>>> ld.lld: error: arch/riscv/built-in.a(kernel/cpu.o):(function riscv_of_processor_hartid: .text+0x2c): relocation R_RISCV_HI20 out of range: 530099 is not in [-524288, 524287]; references .LCPI0_0
> >>> referenced by cpu.c
> >>> defined in arch/riscv/built-in.a(kernel/cpu.o)
> --
>>> ld.lld: error: arch/riscv/built-in.a(kernel/cpu.o):(function riscv_of_parent_hartid: .text+0x160): relocation R_RISCV_HI20 out of range: 529283 is not in [-524288, 524287]; references .L.str
> >>> referenced by cpu.c
> >>> defined in arch/riscv/built-in.a(kernel/cpu.o)
> --
>>> ld.lld: error: arch/riscv/built-in.a(kernel/cpu.o):(function riscv_of_parent_hartid: .text+0x19c): relocation R_RISCV_HI20 out of range: 530099 is not in [-524288, 524287]; references .LCPI1_0
> >>> referenced by cpu.c
> >>> defined in arch/riscv/built-in.a(kernel/cpu.o)
> --
>>> ld.lld: error: init/built-in.a(initramfs.o):(function wait_for_initramfs: .text+0x3c): relocation R_RISCV_HI20 out of range: 529437 is not in [-524288, 524287]; references initramfs_domain
> >>> referenced by initramfs.c
> >>> defined in init/built-in.a(initramfs.o)
> --
>>> ld.lld: error: init/built-in.a(initramfs.o):(function panic_show_mem: .text+0xa8): relocation R_RISCV_HI20 out of range: 530099 is not in [-524288, 524287]; references .LCPI8_0
> >>> referenced by initramfs.c
> >>> defined in init/built-in.a(initramfs.o)
>
next prev parent reply other threads:[~2022-04-03 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 22:08 kernel test robot
2022-04-03 9:40 ` Christophe Leroy [this message]
2022-04-03 13:48 ` [kbuild-all] " Chen, Rong A
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=d403df3f-4277-7800-b583-94bdbd7aa9c5@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
/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