From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kdave-btrfs-devel:misc-next 32/79] fs/btrfs/backref.o: warning: objtool: btrfs_backref_finish_upper_links.cold()+0x4b: unreachable instruction
Date: Thu, 28 May 2020 09:44:57 +0800 [thread overview]
Message-ID: <202005280955.q52Ygbzf%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
tree: https://github.com/kdave/btrfs-devel.git misc-next
head: 036f56e45890058c21dc52207667c779de663ce7
commit: e66c51a111909e0f5917727d57f2bac552131bb0 [32/79] btrfs: backref: rename and move finish_upper_links()
config: x86_64-randconfig-r036-20200527 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout e66c51a111909e0f5917727d57f2bac552131bb0
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> fs/btrfs/backref.o: warning: objtool: btrfs_backref_finish_upper_links.cold()+0x4b: unreachable instruction
---
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: 43274 bytes --]
reply other threads:[~2020-05-28 1:44 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=202005280955.q52Ygbzf%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.