From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: ld.lld: warning: vmlinux.o: DWARF unit at offset 0x000003bb has unsupported version 27439, supported are 2-5
Date: Sat, 15 Feb 2025 07:29:44 +0800 [thread overview]
Message-ID: <202502150718.KRAMO9uu-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Masahiro Yamada <masahiroy@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 04f41cbf03ec7221ab0b179e336f4c805ee55520
commit: 695ed93bb30e03e9f826ee70abdd83f970741a37 kbuild: fix Clang LTO with CONFIG_OBJTOOL=n
date: 2 weeks ago
:::::: branch date: 4 hours ago
:::::: commit date: 2 weeks ago
config: riscv-randconfig-r131-20250214 (https://download.01.org/0day-ci/archive/20250215/202502150718.KRAMO9uu-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20250215/202502150718.KRAMO9uu-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202502150718.KRAMO9uu-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> ld.lld: warning: vmlinux.o: DWARF unit at offset 0x000003bb has unsupported version 27439, supported are 2-5
ld.lld: error: vmlinux.o:(function __folio_migrate_mapping: .text.__folio_migrate_mapping+0xa8): relocation R_RISCV_BRANCH out of range: 4132 is not in [-4096, 4095]; references .LBB10854_127
>>> referenced by ld-temp.o
>>> defined in vmlinux.o
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-14 23:30 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=202502150718.KRAMO9uu-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.