From: lkcl <luke.leighton@gmail.com>
To: Dmitry Selyutin <ghostmansd@gmail.com>,
binutils@sourceware.org, Alan Modra <amodra@gmail.com>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Subject: Re: Plugin-based opcode table
Date: Tue, 17 May 2022 15:01:48 +0100 [thread overview]
Message-ID: <CAPweEDzRUQukJgnFKutun+xJpiPjvTeRSi9_irx=QrebFHg7sQ@mail.gmail.com> (raw)
In-Reply-To: <CAMqzjev3_z+uGbh-0_rdJ06+m5Fn0naeEn5jTpz9Va01JBYSKw@mail.gmail.com>
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.
we're quite happy to do the work (and have the funding from NLnet to do it).
btw one big question, i note that v3.1 prefixed instructions have started
to be added:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=8acf14351c818d956babe50e61711740f378c941
we would need to work out how - in a *plugin* context - how to bring in
SVP64 which uses some of EXT001's [currently] reserved space.
and also how to reserve a known range of the opindex without the plugin
trampling all over the non-plugin (OPF-approved) area. that's a lot
easier once opindex is 16-bit.
l.
next prev parent reply other threads:[~2022-05-17 14:02 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 [this message]
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
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='CAPweEDzRUQukJgnFKutun+xJpiPjvTeRSi9_irx=QrebFHg7sQ@mail.gmail.com' \
--to=luke.leighton@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@gmail.com \
--cc=lkcl@lkcl.net \
/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).