From: lkcl <luke.leighton@gmail.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: Peter Bergner <bergner@linux.ibm.com>,
Dmitry Selyutin <ghostmansd@gmail.com>,
Alan Modra <amodra@gmail.com>,
binutils@sourceware.org, Alain Williams <addw@phcomp.co.uk>
Subject: Re: Plugin-based opcode table
Date: Tue, 31 May 2022 05:06:06 +0100 [thread overview]
Message-ID: <CAPweEDy=hF7JSK8hySZcZH-abGY+G9N-VX8=xFvsZ_kyap=fFA@mail.gmail.com> (raw)
In-Reply-To: <YpVZfBm3igJfDw2c@cleo>
On Tue, May 31, 2022 at 1:14 AM Paul Mackerras <paulus@ozlabs.org> wrote:
>
> Just to clarify something below...
always appreciated, Paul.
> The problem Peter was describing was at the assembly level not the
> machine code level. The lxvd2x instruction still exists in POWER9 and
> does the same thing that it does in POWER8.
ahh right. so an older program compiled prior to the assembler mnemonic
rename will still be binary-compatible.
> That is, the difference is in what bits you get out of the assembler
> when you write "lxvx", rather than a binary compatibility difference.
subtle, and annoying/quirky, but not something that breaks older
programs, thank goodness. important to have clarified because it
would give the false impression (to any future reader of the archives)
of an instability in the Power ISA, which would be bad.
l.
prev parent reply other threads:[~2022-05-31 4:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 12:37 Dmitry Selyutin
2022-05-17 14:01 ` lkcl
2022-05-23 12:59 ` Alan Modra
2022-05-23 13:06 ` Dmitry Selyutin
2022-05-24 5:41 ` Alan Modra
2022-05-24 22:11 ` Dmitry Selyutin
2022-05-29 2:30 ` Peter Bergner
2022-05-29 9:13 ` Luke Kenneth Casson Leighton
2022-05-30 23:55 ` Paul Mackerras
2022-05-31 4:06 ` lkcl [this message]
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='CAPweEDy=hF7JSK8hySZcZH-abGY+G9N-VX8=xFvsZ_kyap=fFA@mail.gmail.com' \
--to=luke.leighton@gmail.com \
--cc=addw@phcomp.co.uk \
--cc=amodra@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@gmail.com \
--cc=paulus@ozlabs.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).