All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jpoimboe:klp-build 43/63] kernel/bounds.c:35:40: error: invalid application of 'sizeof' to incomplete type 'struct jump_entry'
Date: Wed, 25 Jun 2025 16:35:40 +0800	[thread overview]
Message-ID: <202506251600.VKaltOhm-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git klp-build
head:   adb4071ac1d133861613cf55ff4f4d4858313258
commit: aacce3fee88ef9617ea4938a4f53b46974be7202 [43/63] x86/jump_label: Define ELF section entry size for jump labels
config: i386-buildonly-randconfig-002-20250625 (https://download.01.org/0day-ci/archive/20250625/202506251600.VKaltOhm-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250625/202506251600.VKaltOhm-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/202506251600.VKaltOhm-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from kernel/bounds.c:13:
   kernel/bounds.c: In function 'main':
>> kernel/bounds.c:35:40: error: invalid application of 'sizeof' to incomplete type 'struct jump_entry'
      35 |         DEFINE(JUMP_ENTRY_SIZE, sizeof(struct jump_entry));
         |                                        ^~~~~~
   include/linux/kbuild.h:6:69: note: in definition of macro 'DEFINE'
       6 |         asm volatile("\n.ascii \"->" #sym " %0 " #val "\"" : : "i" (val))
         |                                                                     ^~~
   make[3]: *** [scripts/Makefile.build:182: kernel/bounds.s] Error 1 shuffle=2115482694
   make[3]: Target 'prepare' not remade because of errors.
   make[2]: *** [Makefile:1274: prepare0] Error 2 shuffle=2115482694
   make[2]: Target 'prepare' not remade because of errors.
   make[1]: *** [Makefile:248: __sub-make] Error 2 shuffle=2115482694
   make[1]: Target 'prepare' not remade because of errors.
   make: *** [Makefile:248: __sub-make] Error 2 shuffle=2115482694
   make: Target 'prepare' not remade because of errors.


vim +35 kernel/bounds.c

    17	
    18	int main(void)
    19	{
    20		/* The enum constants to put into include/generated/bounds.h */
    21		DEFINE(NR_PAGEFLAGS, __NR_PAGEFLAGS);
    22		DEFINE(MAX_NR_ZONES, __MAX_NR_ZONES);
    23	#ifdef CONFIG_SMP
    24		DEFINE(NR_CPUS_BITS, order_base_2(CONFIG_NR_CPUS));
    25	#endif
    26		DEFINE(SPINLOCK_SIZE, sizeof(spinlock_t));
    27	#ifdef CONFIG_LRU_GEN
    28		DEFINE(LRU_GEN_WIDTH, order_base_2(MAX_NR_GENS + 1));
    29		DEFINE(__LRU_REFS_WIDTH, MAX_NR_TIERS - 2);
    30	#else
    31		DEFINE(LRU_GEN_WIDTH, 0);
    32		DEFINE(__LRU_REFS_WIDTH, 0);
    33	#endif
    34	#if defined(CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE)
  > 35		DEFINE(JUMP_ENTRY_SIZE, sizeof(struct jump_entry));

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-06-25  8:36 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=202506251600.VKaltOhm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jpoimboe@kernel.org \
    --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.