From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [RFC 03/13] objtool: Disassemble code with libopcodes instead of running objdump
Date: Sat, 7 Jun 2025 15:20:35 +0800 [thread overview]
Message-ID: <202506071438.NpC5O1aA-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250606153440.865808-4-alexandre.chartre@oracle.com>
References: <20250606153440.865808-4-alexandre.chartre@oracle.com>
TO: Alexandre Chartre <alexandre.chartre@oracle.com>
Hi Alexandre,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.15 next-20250606]
[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/Alexandre-Chartre/objtool-Move-disassembly-functions-to-a-separated-file/20250606-233948
base: linus/master
patch link: https://lore.kernel.org/r/20250606153440.865808-4-alexandre.chartre%40oracle.com
patch subject: [RFC 03/13] objtool: Disassemble code with libopcodes instead of running objdump
:::::: branch date: 15 hours ago
:::::: commit date: 15 hours ago
config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20250607/202506071438.NpC5O1aA-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250607/202506071438.NpC5O1aA-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/202506071438.NpC5O1aA-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
arch/powerpc/decode.c: In function 'arch_reloc_size':
>> arch/powerpc/decode.c:131:5: warning: declaration of 'arch_disas_info_init' shadows a global declaration [-Wshadow]
131 | int arch_disas_info_init(struct disassemble_info *dinfo)
| ^~~~~~~~~~~~~~~~~~~~
In file included from tools/objtool/include/objtool/check.h:11,
from arch/powerpc/decode.c:5:
tools/objtool/include/objtool/arch.h:107:5: note: shadowed declaration is here
107 | int arch_disas_info_init(struct disassemble_info *dinfo);
| ^~~~~~~~~~~~~~~~~~~~
>> arch/powerpc/decode.c:131:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
131 | int arch_disas_info_init(struct disassemble_info *dinfo)
| ^~~
>> arch/powerpc/decode.c:136:1: error: expected declaration or statement at end of input
136 | }
| ^
arch/powerpc/decode.c: At top level:
>> arch/powerpc/decode.c:131:5: warning: 'arch_disas_info_init' defined but not used [-Wunused-function]
131 | int arch_disas_info_init(struct disassemble_info *dinfo)
| ^~~~~~~~~~~~~~~~~~~~
make[6]: *** [tools/build/Makefile.build:86: tools/objtool/arch/powerpc/decode.o] Error 1
In file included from disas.c:12:
tools/include/tools/dis-asm-compat.h:10:6: error: redeclaration of 'enum disassembler_style'
10 | enum disassembler_style {DISASSEMBLER_STYLE_NOT_EMPTY};
| ^~~~~~~~~~~~~~~~~~
In file included from tools/objtool/include/objtool/arch.h:10,
from disas.c:6:
/usr/include/dis-asm.h:53:6: note: originally defined here
53 | enum disassembler_style
| ^~~~~~~~~~~~~~~~~~
tools/include/tools/dis-asm-compat.h: In function 'init_disassemble_info_compat':
tools/include/tools/dis-asm-compat.h:50:9: error: too few arguments to function 'init_disassemble_info'
50 | init_disassemble_info(info, stream,
| ^~~~~~~~~~~~~~~~~~~~~
/usr/include/dis-asm.h:480:13: note: declared here
480 | extern void init_disassemble_info (struct disassemble_info *dinfo, void *stream,
| ^~~~~~~~~~~~~~~~~~~~~
make[5]: *** [tools/build/Makefile.build:86: tools/objtool/disas.o] Error 1
make[6]: Target '__build' not remade because of errors.
make[5]: *** [tools/build/Makefile.build:142: arch/powerpc] Error 2
make[5]: Target '__build' not remade because of errors.
make[4]: *** [Makefile:65: tools/objtool/objtool-in.o] Error 2
make[4]: Target 'all' not remade because of errors.
make[3]: *** [Makefile:73: objtool] Error 2
make[2]: *** [Makefile:1448: tools/objtool] Error 2
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-07 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 7:20 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-06 17:21 [RFC 03/13] objtool: Disassemble code with libopcodes instead of running objdump kernel test robot
2025-06-06 15:34 [RFC 00/13] objtool: Function validation tracing Alexandre Chartre
2025-06-06 15:34 ` [RFC 03/13] objtool: Disassemble code with libopcodes instead of running objdump Alexandre Chartre
2025-06-07 0:45 ` kernel test robot
2025-06-10 21:22 ` Josh Poimboeuf
2025-06-11 12:23 ` Peter Zijlstra
2025-06-11 13:35 ` Alexandre Chartre
2025-06-11 19:25 ` Josh Poimboeuf
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=202506071438.NpC5O1aA-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.