From: Nathan Chancellor <nathan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Dmitrii Bundin <dmitrii.bundin.a@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev,
kernel test robot <lkp@intel.com>
Subject: Re: [linux-next:master 4627/4736] ld.lld: error: vmlinux.o:(.debug_info+0x2096020d): relocation R_AARCH64_ABS32 out of range: 4295813883 is not in
Date: Fri, 2 Sep 2022 09:29:10 -0700 [thread overview]
Message-ID: <YxIvVmJcKzJrIRzD@dev-arch.thelio-3990X> (raw)
In-Reply-To: <202209021113.imFYddaU-lkp@intel.com>
+ Andrew, Dmitrii, and Nick
On Fri, Sep 02, 2022 at 11:26:27AM +0800, kernel test robot wrote:
> CC: Linux Memory Management List <linux-mm@kvack.org>
> TO: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: Linux Memory Management List <linux-mm@kvack.org>
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: e47eb90a0a9ae20b82635b9b99a8d0979b757ad8
> commit: 12c674aa7e797864f36a4e9dbc2cf20930c1f6fe [4627/4736] kbuild: add debug level and macro defs options
> config: arm64-randconfig-r021-20220901 (https://download.01.org/0day-ci/archive/20220902/202209021113.imFYddaU-lkp@intel.com/config)
> compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project c55b41d5199d2394dd6cdb8f52180d8b81d809d4)
> 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 arm64 cross compiling tool for clang build
> # apt-get install binutils-aarch64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=12c674aa7e797864f36a4e9dbc2cf20930c1f6fe
> 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 12c674aa7e797864f36a4e9dbc2cf20930c1f6fe
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> ld.lld: error: vmlinux.o:(.debug_info+0x2096020d): relocation R_AARCH64_ABS32 out of range: 4295813883 is not in [-2147483648, 4294967295]
> >>> referenced by xarray.c; consider recompiling with -fdebug-types-section to reduce size of debug sections
It seems like CONFIG_DEBUG_MACRO_DEFINITIONS can blow up the size of the
kernel image significantly. Perhaps it should be marked with a
depends on !COMPILE_TEST
to avoid having all{mod,yes}config and randconfigs trip over it?
Cheers,
Nathan
next prev parent reply other threads:[~2022-09-02 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 3:26 [linux-next:master 4627/4736] ld.lld: error: vmlinux.o:(.debug_info+0x2096020d): relocation R_AARCH64_ABS32 out of range: 4295813883 is not in kernel test robot
2022-09-02 16:29 ` Nathan Chancellor [this message]
2022-09-02 17:27 ` Dmitrii Bundin
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=YxIvVmJcKzJrIRzD@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmitrii.bundin.a@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@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