Re: {standard input}:924: Error: unrecognized opcode: `eieio'

From: Pali Rohár
Date: Sat Apr 22 2023 - 09:58:48 EST


On Saturday 22 April 2023 21:53:23 kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8e41e0a575664d26bb87e012c39435c4c3914ed9
> commit: ff7c76f66d8bad4e694c264c789249e1d3a8205d powerpc/boot: Don't always pass -mcpu=powerpc when building 32-bit uImage
> date: 3 months ago
> config: powerpc-buildonly-randconfig-r006-20230422 (https://download.01.org/0day-ci/archive/20230422/202304222120.WcBMaHXo-lkp@xxxxxxxxx/config)
> compiler: powerpc-linux-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff7c76f66d8bad4e694c264c789249e1d3a8205d
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout ff7c76f66d8bad4e694c264c789249e1d3a8205d
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=powerpc olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@xxxxxxxxx>
> | Link: https://lore.kernel.org/oe-kbuild-all/202304222120.WcBMaHXo-lkp@xxxxxxxxx/
>
> All errors (new ones prefixed by >>):
>
> {standard input}: Assembler messages:
> >> {standard input}:924: Error: unrecognized opcode: `eieio'
> {standard input}:1094: Error: unrecognized opcode: `eieio'
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests

Hello! What is that? In this error report there is no compile log, nor
any file / line. And "Link:" line from above error report does not work.

Intel, can you look at your robot? This looks some bug in error reporting.