From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [tip:objtool/core 2/16] sound/soc/sof/snd-sof.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
Date: Tue, 3 Dec 2024 05:06:04 +0800 [thread overview]
Message-ID: <202412030541.tAmAZH2V-lkp@intel.com> (raw)
CC: linux-kernel@vger.kernel.org
CC: x86@kernel.org
TO: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git objtool/core
head: e7e0eb53c2f0f68fe2577472ce2802a4efd9d7ce
commit: 22c3d58079688b697f36d670616e463cbb14d058 [2/16] objtool: Convert ANNOTATE_NOENDBR to ANNOTATE
config: x86_64-buildonly-randconfig-006-20241203 (https://download.01.org/0day-ci/archive/20241203/202412030541.tAmAZH2V-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241203/202412030541.tAmAZH2V-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/202412030541.tAmAZH2V-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/sof/snd-sof.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> sound/pci/hda/snd-hda-intel.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> sound/soc/sof/intel/snd-sof-intel-hda-common.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
In file included from drivers/fsi/fsi-core.c:31:
In file included from include/trace/events/fsi.h:245:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:21:
In file included from include/linux/trace_events.h:6:
In file included from include/linux/ring_buffer.h:5:
In file included from include/linux/mm.h:2223:
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
1 warning generated.
>> drivers/fsi/fsi-core.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
In file included from drivers/spmi/spmi.c:18:
In file included from include/trace/events/spmi.h:136:
In file included from include/trace/define_trace.h:113:
In file included from include/trace/trace_events.h:21:
In file included from include/linux/trace_events.h:6:
In file included from include/linux/ring_buffer.h:5:
In file included from include/linux/mm.h:2223:
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
1 warning generated.
>> drivers/spmi/spmi.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-02 21:06 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=202412030541.tAmAZH2V-lkp@intel.com \
--to=lkp@intel.com \
--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 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.