public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] rs6000: Improve .machine
Date: Tue, 15 Mar 2022 15:29:23 +0100	[thread overview]
Message-ID: <1ca1030d-daea-01d1-9932-64eb2efb4aa6@embedded-brains.de> (raw)
In-Reply-To: <20220310101125.GV614@gate.crashing.org>

Hello Segher,

On 10/03/2022 11:11, Segher Boessenkool wrote:
> On Thu, Mar 10, 2022 at 09:25:21AM +0100, Sebastian Huber wrote:
>> On 04/03/2022 17:51, Segher Boessenkool wrote:
>>> This adds more correct .machine for most older CPUs.  It should be
>>> conservative in the sense that everything we handled before we handle at
>>> least as well now.  This does not yet revamp the server CPU handling, it
>>> is too risky at this point in time.
>>>
>>> Tested on powerpc64-linux {-m32,-m64}.  Also manually tested with all
>>> -mcpu=, and the output of that passed through the GNU assembler.
>>>
>>> I plan to commit this later today.
>> Could this be back ported to GCC 10 and 11? I would fix the following
>> issue for -mcpu=405:
>>
>> Error: unrecognized opcode: `dlmzb.'
> Good to hear!
> 
> Unfortunately there is PR104829 about this commit.  I don't see how the
> commit can break anything (that wasn't already broken); it's not clear
> how it happens at all, and neither me nor colleagues could reproduce it
> so far.
> 
> So I won't yet backport it, but first wait what happens here.

now that the PR104829 is fixed could I back port

Segher Boessenkool (2):
   rs6000: Improve .machine
   rs6000: Do not use rs6000_cpu for .machine ppc and ppc64 (PR104829)

to GCC 10 and 11?

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

  reply	other threads:[~2022-03-15 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 16:51 Segher Boessenkool
2022-03-07 20:53 ` Joseph Myers
2022-03-07 21:57   ` Segher Boessenkool
2022-03-10  8:25 ` Sebastian Huber
2022-03-10 10:11   ` Segher Boessenkool
2022-03-15 14:29     ` Sebastian Huber [this message]
2022-03-15 22:29       ` Segher Boessenkool
2022-04-04  9:31         ` Sebastian Huber
2022-06-20  7:48           ` Sebastian Huber
2022-06-20 18:52             ` Segher Boessenkool

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=1ca1030d-daea-01d1-9932-64eb2efb4aa6@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).