public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: lkcl <luke.leighton@gmail.com>
To: Dmitry Selyutin <ghostmansd@gmail.com>,binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH] ppc/svp64: support svshape2 instruction
Date: Thu, 08 Sep 2022 20:03:19 +0100	[thread overview]
Message-ID: <A9336031-C76E-4F57-9298-0DA6EBA38CFA@gmail.com> (raw)
In-Reply-To: <CAMqzjeso4fOvRNRCwJtFFuewGTSBANvnVg+rO6c4VY9ufLH4+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

On September 8, 2022 7:34:32 PM GMT+01:00, Dmitry Selyutin <ghostmansd@gmail.com> wrote:

> This is a tricky part. svshape2 shares some of its bits with svshape;
> we reserve 0b1000 and 0b1001 values from svshape for svshape2.

(background):

in hardware all 16 combinations are sent to the exact same unit.
the slightly different Form (SVM2 vs SVM because the opcode
args are different bitwidths) is for the convenience of the
assembly writer.

(further background):

svshape is insanely powerful, the sort of thing i revered in
supercomputers from the 90s.  it provides Matrix "Structure
Packing" schedules, DCT/FFT, Parallel Reduction, it's pretty
mental.  all in-place: no more loop-unrolling, no more transpose
copying of regs.

l.

  reply	other threads:[~2022-09-08 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 18:25 Dmitry Selyutin
2022-09-08 18:34 ` Dmitry Selyutin
2022-09-08 19:03   ` lkcl [this message]
2022-09-09  9:22   ` Dmitry Selyutin
2022-09-12  6:24 ` Jan Beulich
2022-09-12  8:43   ` Dmitry Selyutin
2022-09-12 10:30   ` 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=A9336031-C76E-4F57-9298-0DA6EBA38CFA@gmail.com \
    --to=luke.leighton@gmail.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ghostmansd@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).