From: Peter Bergner <bergner@linux.ibm.com>
To: Waldemar Brodkorb <wbx@openadk.org>, binutils@sourceware.org
Subject: Re: regression with binutils 2.28 for ppc
Date: Wed, 16 Feb 2022 08:32:11 -0600 [thread overview]
Message-ID: <a70f8992-5b90-d5d3-a533-ae01fba3153e@linux.ibm.com> (raw)
In-Reply-To: <Ygz9rx/VljP5Jnfg@waldemar-brodkorb.de>
On 2/16/22 7:35 AM, Waldemar Brodkorb wrote:
> since commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a I am getting
> following error when building a Linux Kernel targeting
> qemu-system-ppc (-M macppc).
>
> {standard input}: Assembler messages:
> {standard input}:2156: Error: unrecognized opcode: `ptesync'
> gmake[8]: *** [scripts/Makefile.build:288: arch/powerpc/lib/sstep.o]
> Error 1
> gmake[7]: *** [scripts/Makefile.build:550: arch/powerpc/lib] Error 2
> gmake[6]: *** [Makefile:1831: arch/powerpc] Error 2
> gmake[5]: ***
> [/home/wbx/embedded-test/openadk/mk/kernel-build.mk:91:
> /home/wbx/embedded-test/openadk/build_qemu-ppc-macppc_uclibc-ng_hard/linux/vmlinux]
> Error 2
The ptesync insn is enabled with the PPC64 flag, so should be available for
all 64-bit assembles and disabled for all 32-bit assembles. What assembler
options are you using? It's hard to tell whether you are building a
64-bit kernel, in which ptesync should be fine or whether you are building
a 32-bit kernel, in which case, ptesync would be a kernel error (for using it).
Peter
next prev parent reply other threads:[~2022-02-16 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 13:35 Waldemar Brodkorb
2022-02-16 14:32 ` Peter Bergner [this message]
2022-02-16 18:24 ` Peter Bergner
2022-02-17 9:28 ` Waldemar Brodkorb
2022-02-17 20:03 ` Peter Bergner
2022-02-18 1:34 ` Alan Modra
2022-02-18 4:21 ` Peter Bergner
2022-02-20 11:58 ` Alan Modra
2022-02-23 8:51 ` Alan Modra
2022-02-23 17:34 ` Waldemar Brodkorb
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=a70f8992-5b90-d5d3-a533-ae01fba3153e@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=binutils@sourceware.org \
--cc=wbx@openadk.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).