public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: lkcl <luke.leighton@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Dmitry Selyutin <ghostmansd@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH v6 3/7] ppc/svp64: support setvl instructions
Date: Sun, 21 Aug 2022 17:04:14 +0100	[thread overview]
Message-ID: <CAPweEDyuKeuAZ41vkz_MNkQ+759u2BZQBr59D7t-WtYt_Mij8Q@mail.gmail.com> (raw)
In-Reply-To: <e8d12a0d-9c38-e2b9-61ce-2466efea85ff@suse.com>

On Sun, Aug 21, 2022 at 3:53 PM Jan Beulich <jbeulich@suse.com> wrote:
> On 15.08.2022 14:58, lkcl wrote:
> > ah appreciated, i've added examples.  more will be needed now that
> > there's also setvl-from-CTR as well.
>
> Since you've added the further examples without altering the first
> register operand for the expansion of setvli - is that really meant
> to be r5, not r0?

well-spotted: the addition of the CTR mode post-dates the creation
of those pseudo-ops, i've now corrected them.  it is slightly irksome
that the cost of adding CTR mode was at the expense of losing the
ability to set RT to an immediate, but this may be achieved with
addi RT,0,#N. go figure.

> Is there any preferred way for providing feedback, just in case I
> would spot further little issues? I've responded to the patches
> to binutils mainly because I didn't know anything "better" ...

appreciated. in order of approx precedence (coincidentally,
reverse-convenience):

* directly on the bugtracker bugs.libre-soc.org although contact
  me privately about that, i had to disable account-creation after
  someone used the bugtracker to advertise juniper networks at us
* the mailing list (mailman: i can authorise sending permission if
   you prefer not to subscribe: i.e. just send, and i'll deal with it)
   https://lists.libre-soc.org/mailman/listinfo/libre-soc-dev
* IRC - libera.chat - #libre-soc channel: if you prefer there is a
   Matrix Bridge (run by the libera team) and yet _another_ way
   is via the OPF's mattermost bridge
   https://chat.openpower.foundation/opf/channels/libre-soc
   all messages are logged  https://libre-soc.org/irclog/index.html

as we're under Audit Conditions (EU Funding, NLnet "works for
public good") everything is logged/public, but obviously if you're
used to FOSS then nothing's new :)

l.

  reply	other threads:[~2022-08-21 16:04 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 19:08 [PATCH 0/5] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-06-17 19:08 ` [PATCH 1/5] svp64: support LibreSOC architecture Dmitry Selyutin
2022-06-17 19:08 ` [PATCH 2/5] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-06-17 19:08 ` [PATCH 3/5] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-06-17 19:08 ` [PATCH 4/5] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-06-19 23:49 ` [PATCH 0/5] ppc/svp64: support SVP64 and its first insns Alan Modra
2022-06-21 11:55   ` Dmitry Selyutin
2022-06-21 11:51 ` [PATCH v2 " Dmitry Selyutin
2022-06-21 11:51   ` [PATCH v2 1/5] ppc/svp64: support LibreSOC architecture Dmitry Selyutin
2022-06-21 11:51   ` [PATCH v2 2/5] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-06-21 18:25     ` Peter Bergner
2022-06-21 18:39       ` Peter Bergner
2022-06-21 11:51   ` [PATCH v2 3/5] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-06-21 11:51   ` [PATCH v2 4/5] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-06-22  6:41   ` [PATCH v2 0/5] ppc/svp64: support SVP64 and its first insns Jan Beulich
2022-06-22  6:44   ` Jan Beulich
2022-06-22  6:57     ` Dmitry Selyutin
2022-06-23 19:37   ` [PATCH v3 0/6] " Dmitry Selyutin
2022-06-23 19:37     ` [PATCH v3 1/6] ppc/svp64: support LibreSOC architecture Dmitry Selyutin
2022-06-23 19:37     ` [PATCH v3 2/6] ppc: introduce non-zero operand Dmitry Selyutin
2022-06-23 19:58       ` lkcl
2022-06-23 19:37     ` [PATCH v3 3/6] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-06-23 19:37     ` [PATCH v3 4/6] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-06-23 19:37     ` [PATCH v3 5/6] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-06-23 19:37     ` [PATCH v3 6/6] ppc/svp64: support svremap instruction Dmitry Selyutin
2022-06-23 19:45     ` [PATCH v3 0/6] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-06-23 20:10       ` Dmitry Selyutin
2022-06-24 11:38       ` Draft Simple-V roadmap for Power ISA (was: [PATCH v3 0/6] ppc/svp64: support SVP64 and its first insns) lkcl
2022-06-23 20:08     ` [PATCH v4 0/6] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 1/6] ppc/svp64: support LibreSOC architecture Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 2/6] ppc: introduce non-zero operand flag Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 3/6] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 4/6] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 5/6] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-06-23 20:08       ` [PATCH v4 6/6] ppc/svp64: support svremap instruction Dmitry Selyutin
2022-06-26 18:59       ` [PATCH v5 0/7] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-06-26 18:59         ` [PATCH v5 1/7] ppc/svp64: support LibreSOC architecture Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 2/7] ppc: introduce non-zero operand flag Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 3/7] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 4/7] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 5/7] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 6/7] ppc/svp64: support svremap instruction Dmitry Selyutin
2022-06-26 19:00         ` [PATCH v5 7/7] ppc/svp64: support svindex instruction Dmitry Selyutin
2022-07-25 13:10         ` [PATCH v6 0/7] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 1/7] ppc/svp64: support LibreSOC architecture Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 2/7] ppc: introduce non-zero operand flag Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 3/7] ppc/svp64: support setvl instructions Dmitry Selyutin
2022-08-15  6:18             ` Jan Beulich
2022-08-15 12:58               ` lkcl
2022-08-15 13:08                 ` Dmitry Selyutin
2022-08-21 14:53                 ` Jan Beulich
2022-08-21 16:04                   ` lkcl [this message]
2022-07-25 13:10           ` [PATCH v6 4/7] ppc/svp64: support svstep instructions Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 5/7] ppc/svp64: support svshape instruction Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 6/7] ppc/svp64: support svremap instruction Dmitry Selyutin
2022-07-25 13:10           ` [PATCH v6 7/7] ppc/svp64: support svindex instruction Dmitry Selyutin
2022-07-26 13:14           ` [PATCH v6 0/7] ppc/svp64: support SVP64 and its first insns Dmitry Selyutin
2022-07-27  4:53             ` Alan Modra
2022-07-27  6:38               ` lkcl
2022-08-11  9:14           ` Alan Modra
2022-08-11 10:48             ` [PATCH 0/5] " lkcl
2022-08-12  3:30             ` [PATCH v6 0/7] " Dmitry Selyutin

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=CAPweEDyuKeuAZ41vkz_MNkQ+759u2BZQBr59D7t-WtYt_Mij8Q@mail.gmail.com \
    --to=luke.leighton@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ghostmansd@gmail.com \
    --cc=jbeulich@suse.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).