From: kernel test robot <lkp@intel.com>
To: Jiawei Zhao <Phoenix500526@163.com>, ast@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libbpf: add SIB addressing mode support for x86-64 USDT arguments
Date: Wed, 30 Jul 2025 11:36:23 +0800 [thread overview]
Message-ID: <202507301122.2gtH7n4r-lkp@intel.com> (raw)
In-Reply-To: <20250729125244.28364-1-Phoenix500526@163.com>
Hi Jiawei,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/net]
[also build test ERROR on bpf-next/master bpf/master linus/master v6.16 next-20250729]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jiawei-Zhao/libbpf-add-SIB-addressing-mode-support-for-x86-64-USDT-arguments/20250729-205449
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git net
patch link: https://lore.kernel.org/r/20250729125244.28364-1-Phoenix500526%40163.com
patch subject: [PATCH] libbpf: add SIB addressing mode support for x86-64 USDT arguments
config: arm-randconfig-001-20250730 (https://download.01.org/0day-ci/archive/20250730/202507301122.2gtH7n4r-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project bcd0d972247154336dd1321f1fded818e46671d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250730/202507301122.2gtH7n4r-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/oe-kbuild-all/202507301122.2gtH7n4r-lkp@intel.com/
All errors (new ones prefixed by >>):
>> usdt.c:1301:7: error: mixing declarations and code is a C99 extension [-Werror,-Wdeclaration-after-statement]
1301 | int idx_reg_off = calc_pt_regs_off(idx_reg_name);
| ^
1 error generated.
make[6]: *** [tools/build/Makefile.build:85: tools/bpf/resolve_btfids/libbpf/staticobjs/usdt.o] Error 1 shuffle=2731265819
make[6]: Target '__build' not remade because of errors.
make[5]: *** [Makefile:152: tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2 shuffle=2731265819
make[5]: Target 'tools/bpf/resolve_btfids/libbpf/libbpf.a' not remade because of errors.
make[4]: *** [Makefile:61: tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2 shuffle=2731265819
make[4]: Target 'all' not remade because of errors.
make[3]: *** [Makefile:76: bpf/resolve_btfids] Error 2 shuffle=2731265819
make[2]: *** [Makefile:1443: tools/bpf/resolve_btfids] Error 2 shuffle=2731265819
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2 shuffle=2731265819
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2 shuffle=2731265819
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-30 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 12:52 Jiawei Zhao
2025-07-30 3:36 ` kernel test robot [this message]
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=202507301122.2gtH7n4r-lkp@intel.com \
--to=lkp@intel.com \
--cc=Phoenix500526@163.com \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®