From: kernel test robot <lkp@intel.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: /tmp/ccB3TqZP.s:15: Error: unrecognized opcode: `wrtee'
Date: Wed, 13 Sep 2023 14:12:21 +0800 [thread overview]
Message-ID: <202309131416.qCTju9Td-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3669558bdf354cd352be955ef2764cde6a9bf5ec
commit: f5df87b855fd835ff0f4928575adbf4f5302bb40 powerpc/build: Remove -pipe from compilation flags
date: 3 months ago
config: powerpc-buildonly-randconfig-r006-20220531 (https://download.01.org/0day-ci/archive/20230913/202309131416.qCTju9Td-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230913/202309131416.qCTju9Td-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/202309131416.qCTju9Td-lkp@intel.com/
All errors (new ones prefixed by >>):
/tmp/ccB3TqZP.s: Assembler messages:
>> /tmp/ccB3TqZP.s:15: Error: unrecognized opcode: `wrtee'
/tmp/ccB3TqZP.s:64: Error: unrecognized opcode: `wrteei'
--
/tmp/ccFA32eu.s: Assembler messages:
/tmp/ccFA32eu.s:240: Error: unrecognized opcode: `wrtee'
/tmp/ccFA32eu.s:304: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:2159: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:3451: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:3710: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:7053: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:7507: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:8171: Error: unrecognized opcode: `wrteei'
>> /tmp/ccFA32eu.s:8582: Error: unrecognized opcode: `mbar'
/tmp/ccFA32eu.s:12273: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:12607: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:13473: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:13726: Error: unrecognized opcode: `wrteei'
/tmp/ccFA32eu.s:13965: Error: unrecognized opcode: `wrteei'
--
/tmp/cczs4OOF.s: Assembler messages:
/tmp/cczs4OOF.s:2812: Error: unrecognized opcode: `mullhwu'
/tmp/cczs4OOF.s:2830: Error: unrecognized opcode: `mullhwu'
>> /tmp/cczs4OOF.s:19996: Error: unrecognized opcode: `mullhwu.'
/tmp/cczs4OOF.s:20170: Error: unrecognized opcode: `mullhwu'
--
/tmp/ccv20csa.s: Assembler messages:
>> /tmp/ccv20csa.s:24: Error: unrecognized opcode: `mtdcr'
>> /tmp/ccv20csa.s:27: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:74: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:77: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:735: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:742: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:749: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:757: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:764: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:771: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:778: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:786: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:897: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:900: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:903: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:909: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:915: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:918: Error: unrecognized opcode: `mfdcr'
/tmp/ccv20csa.s:921: Error: unrecognized opcode: `mtdcr'
/tmp/ccv20csa.s:927: Error: unrecognized opcode: `mtdcr'
--
/tmp/ccAshUsv.s: Assembler messages:
/tmp/ccAshUsv.s:299: Error: unrecognized opcode: `iccci'
>> /tmp/ccAshUsv.s:419: Error: unrecognized opcode: `tlbwe'
/tmp/ccAshUsv.s:420: Error: unrecognized opcode: `tlbwe'
/tmp/ccAshUsv.s:421: Error: unrecognized opcode: `tlbwe'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-13 6:15 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=202309131416.qCTju9Td-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®