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/ccDME0uz.s:1274: Error: unrecognized opcode: `ldbrx'
Date: Wed, 15 Nov 2023 18:36:52 +0800 [thread overview]
Message-ID: <202311151805.cYO3x9wy-lkp@intel.com> (raw)
Hi Nicholas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c42d9eeef8e5ba9292eda36fd8e3c11f35ee065c
commit: f5df87b855fd835ff0f4928575adbf4f5302bb40 powerpc/build: Remove -pipe from compilation flags
date: 5 months ago
config: powerpc-cell_defconfig (https://download.01.org/0day-ci/archive/20231115/202311151805.cYO3x9wy-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231115/202311151805.cYO3x9wy-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/202311151805.cYO3x9wy-lkp@intel.com/
All errors (new ones prefixed by >>):
/tmp/ccDME0uz.s: Assembler messages:
>> /tmp/ccDME0uz.s:1274: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:1276: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:1278: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:1279: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:2033: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:2039: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:2040: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:7758: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:8366: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:8493: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:8495: Error: unrecognized opcode: `ldbrx'
/tmp/ccDME0uz.s:8502: Error: unrecognized opcode: `ldbrx'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-15 10:37 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=202311151805.cYO3x9wy-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®