Re: [akpm-mm:mm-unstable 340/601] include/linux/compiler_types.h:702:38: error: call to '__compiletime_assert_501' declared with attribute error: BUILD_BUG failed
Andrew Morton <[email protected]> Sat, 25 Jul 2026 19:51:08 -0700
| Newsgroups | dev.linux.lists.oe-kbuild-all,org.kernel.vger.mm-commits,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 25 Jul 2026 08:56:41 +0800 kernel test robot <[email protected]> wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable > head: c04df384b55dd9dcf72c36b661becb5aaba371a9 > commit: d2aed7c02fafacb9d055a2f683ac12e977ef16e0 [340/601] mm: preserve RWP marker across PTE rewrites > config: sparc64-randconfig-r134-20260725 (https://download.01.org/0day-ci/archive/20260725/[email protected]/config) > compiler: sparc64-linux-gcc (GCC) 8.5.0 > sparse: v0.6.5-rc1 > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260725/[email protected]/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 <[email protected]> > | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/ > > All errors (new ones prefixed by >>): > > In file included from <command-line>: > mm/huge_memory.c: In function 'move_pages_huge_pmd': > >> include/linux/compiler_types.h:702:38: error: call to '__compiletime_assert_501' declared with attribute error: BUILD_BUG failed > _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) > ^ > include/linux/compiler_types.h:683:4: note: in definition of macro '__compiletime_assert' > prefix ## suffix(); \ Well dang. I can't reproduce with sparc64 gcc-15.2.0. Documentation/process/changes.rst says we support 8,1, released in 2018. Your 8.5 was released in 2021 so perhaps three other people are still using it :( https://www.kernel.org/pub/tools/crosstool/ doesn't appear to have sparc64 gcc-8.5 so I gave up. So I dunno. I'm inclined to ignore and assume that if someone else hits this one day, they'll either fix it or provide us with enough details to figure it out.