From: Alan Modra <amodra@gmail.com>
To: lkcl <luke.leighton@gmail.com>
Cc: Dmitry Selyutin <ghostmansd@gmail.com>,
binutils@sourceware.org,
Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Subject: Re: Plugin-based opcode table
Date: Mon, 23 May 2022 22:29:05 +0930 [thread overview]
Message-ID: <YouFGavJxwKgUw6H@squeak.grove.modra.org> (raw)
In-Reply-To: <CAPweEDzRUQukJgnFKutun+xJpiPjvTeRSi9_irx=QrebFHg7sQ@mail.gmail.com>
On Tue, May 17, 2022 at 03:01:48PM +0100, lkcl wrote:
> On May 17, 2022 1:37:36 PM GMT+01:00, Dmitry Selyutin
> <ghostmansd@gmail.com> wrote:
>
> > We've been thinking of some plugin, with obvious candidates being
> >dlopen/dlsym combo. Sure the code will be public, as well as the whole
> >work around libresoc and SVP64.
>
> ... but it would not be "endorsed" - implicitly and accidentally - by
> the binutils team making decisions that are at odds with the direction
> set by the OpenPOWER Foundation.
>
> prior to approval yes-or-no by OPF, a plugin system would not, i feel,
> actually need endorsement *by* the OpenPOWER Foundation to go ahead:
> that's more down to you, Alan.
I don't see any need for the artificial boundaries you might get with
a plugin, whatever that might look like. ppc-opc.c already supports
multiple incompatible powerpc cpu implementations, including ones that
depart significantly from current powerpc ISA documentation. Your new
SVP64 design is not an orphan in that respect. I do not want to see
"plugin" silliness out of fear of stepping on OPF's toes.
The fact that some cpu is supported in ppc-opc.c has no bearing on ISA
direction. The binutils project doesn't have that power, nor should
it.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-05-23 12:59 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 [this message]
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
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=YouFGavJxwKgUw6H@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@gmail.com \
--cc=lkcl@lkcl.net \
--cc=luke.leighton@gmail.com \
/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).