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: Mon, 15 Aug 2022 13:58:58 +0100	[thread overview]
Message-ID: <CAPweEDzG4WrE0hM-HEszcmbsjEL8eFpt025VJghnG8A0rky=1w@mail.gmail.com> (raw)
In-Reply-To: <d21b747b-2c40-a3c7-c2d5-d001da2f081b@suse.com>

On Mon, Aug 15, 2022 at 7:18 AM Jan Beulich <jbeulich@suse.com> wrote:

> On 25.07.2022 15:10, Dmitry Selyutin via Binutils wrote:
> > +Disassembly of section \.text:
> > +0+ <\.text>:
> > +.*:  (37 00 00 58|58 00 00 37)       setvl.  r0,r0,1,0,0,0
> Out of curiosity - was it intentional to omit a case with the last
> operand non-zero?

one for Dmitry - i believe these are all auto-generated?

> > @@ -6769,6 +6789,9 @@ const struct powerpc_opcode powerpc_opcodes[] = {
> > +{"setvl",    SVL(22,27,0),   SVL_MASK,       SVP64,  PPCVLE, {RT, RA, SVi, vf, vs, ms}},
> > +{"setvl.",   SVL(22,27,1),   SVL_MASK,       SVP64,  PPCVLE, {RT, RA, SVi, vf, vs, ms}},

> According to the web page SETVL has a number of pseudos.

yes.

> I guess you've omitted those for simplicity in the initial submission.

and because there's a python-based (very-easy-to-hack) program
which does the same job as gas, turning SVP64 assembler into
".long xxx; v3.0opcode", and it doesn't have pseudo-ops.

> I'd like to point out though that the web page isn't really
> crystal clear as to, in particular, the Rc field's applicability
> to every one of the pseudos.

ah appreciated, i've added examples.  more will be needed now that
there's also setvl-from-CTR as well.

> (There's also a typo or two which
> makes things a little ambiguous, but there it's reasonably clear
> what is actually meant.)

appreciated.  any feedback is more than welcome.  context there:
despite now being an Open ISA the amount of attention Power is
getting is surprisingly low.  hence any assistance and feedback
is all the more precious.

l.

  reply	other threads:[~2022-08-15 12:59 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 [this message]
2022-08-15 13:08                 ` Dmitry Selyutin
2022-08-21 14:53                 ` Jan Beulich
2022-08-21 16:04                   ` lkcl
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='CAPweEDzG4WrE0hM-HEszcmbsjEL8eFpt025VJghnG8A0rky=1w@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).