From: kbuild test robot <lkp@intel.com>
To: Dirk Mueller <dmueller@suse.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: ld.lld: warning: lld uses blx instruction, no object with architecture supporting feature detected
Date: Wed, 1 Apr 2020 05:20:13 +0800 [thread overview]
Message-ID: <202004010505.30nygaXZ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 42595ce90b9d4a6b9d8c5a1ea78da4eeaf7e086a
commit: e33a814e772cdc36436c8c188d8c42d019fda639 scripts/dtc: Remove redundant YYLOC global declaration
date: 4 days ago
config: arm-randconfig-a001-20200401 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 5227fa0c72ce55927cf4849160acb00442489937)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout e33a814e772cdc36436c8c188d8c42d019fda639
# save the attached .config to linux build tree
COMPILER=clang make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> ld.lld: warning: lld uses blx instruction, no object with architecture supporting feature detected
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27525 bytes --]
next reply other threads:[~2020-03-31 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 21:20 kbuild test robot [this message]
2020-04-01 17:56 ` ld.lld: warning: lld uses blx instruction, no object with architecture supporting feature detected Nick Desaulniers
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=202004010505.30nygaXZ%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=david@gibson.dropbear.id.au \
--cc=dmueller@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 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).