From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: ld.lld: error: section .bss virtual address range overlaps with .ARM.exidx
Date: Fri, 17 Jul 2020 02:55:27 +0800 [thread overview]
Message-ID: <202007170223.ANI7l3Rs%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
CC: linux-kernel(a)vger.kernel.org
TO: Nathan Huckleberry <nhuck15@gmail.com>
CC: Russell King <rmk+kernel@armlinux.org.uk>
CC: Nick Desaulniers <ndesaulniers@google.com>
Hi Nathan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f8456690ba8eb18ea4714e68554e242a04f65cff
commit: 6dc5fd93b2f1ef75d5e50fced8cb193811f25f22 ARM: 8900/1: UNWINDER_FRAME_POINTER implementation for Clang
date: 11 months ago
config: arm-randconfig-r026-20200716 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ed6b578040a85977026c93bf4188f996148f3218)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
git checkout 6dc5fd93b2f1ef75d5e50fced8cb193811f25f22
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
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 >>):
>> ld.lld: error: section .bss virtual address range overlaps with .ARM.exidx
>>> .bss range is [0x945000, 0x1176CB3]
>>> .ARM.exidx range is [0xDC9360, 0xDC936F]
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24480 bytes --]
reply other threads:[~2020-07-16 18:55 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=202007170223.ANI7l3Rs%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.