public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: binutils@sourceware.org, Alan Modra <amodra@gmail.com>
Subject: Re: regression with binutils 2.28 for ppc
Date: Thu, 17 Feb 2022 14:03:24 -0600	[thread overview]
Message-ID: <8b8a3144-5c59-786f-a2ba-6f8813d60845@linux.ibm.com> (raw)
In-Reply-To: <Yg4VRvNLrKoJxrzo@waldemar-brodkorb.de>

On 2/17/22 3:28 AM, Waldemar Brodkorb wrote:
> -mcpu=powerpc -mbig-endian -m32 -msoft-float -mcpu=powerpc64 -mno-altivec -mno-vsx

So a 32-bit compile, which is why the assembler complains about ptesync.
You could try adding -Wa,-mppc64 or -Wa,-many to your options as a work around.
Newish GCCs removed passing -many to the assembler and the commit you
mentioned changed handling of sticky cpu options which is exposing the
issue.  

The use of those ptesyncs in the kernel really needs to be audited though!
If they are legitimate, then the inline assembler needs to wrap their
use with ".machine push ; .machine ppc64 ; ptesync ; .machine pop".

Peter



  reply	other threads:[~2022-02-17 20:03 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
2022-02-16 18:24   ` Peter Bergner
2022-02-17  9:28     ` Waldemar Brodkorb
2022-02-17 20:03       ` Peter Bergner [this message]
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=8b8a3144-5c59-786f-a2ba-6f8813d60845@linux.ibm.com \
    --to=bergner@linux.ibm.com \
    --cc=amodra@gmail.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).