public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp.gcc@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: rdapp.gcc@gmail.com,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	"richard.sandiford" <richard.sandiford@arm.com>,
	krebbel <krebbel@linux.ibm.com>, uweigand <uweigand@de.ibm.com>,
	linkw@linux.ibm.com
Subject: Re: [PATCH V2] VECT: Support LEN_MASK_ LOAD/STORE to support flow control for length loop control
Date: Thu, 15 Jun 2023 11:18:28 +0200	[thread overview]
Message-ID: <93123844-a2a8-90ab-d47a-6f859fb3a8d6@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2306150914360.4723@jbgna.fhfr.qr>

> Meh, PoP is now behind a paywall, trying to get through ... I wonder
> if there's a nice online html documenting the s390 len_load/store
> instructions to better understand the need for the bias.

https://publibfp.dhe.ibm.com/epubs/pdf/a227832c.pdf

Look for vector load with length (store).  The length operand specifies
the highest bytes to load instead of the actual length.

Regards
 Robin

  reply	other threads:[~2023-06-15  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  4:14 juzhe.zhong
2023-06-15  8:06 ` Richard Biener
2023-06-15  8:47   ` juzhe.zhong
2023-06-15  8:58     ` Robin Dapp
2023-06-15  9:01       ` juzhe.zhong
2023-06-15  9:15       ` Richard Biener
2023-06-15  9:18         ` Robin Dapp [this message]
2023-06-15  9:20           ` Robin Dapp
2023-06-15  9:52           ` Richard Biener
2023-06-15 10:08             ` juzhe.zhong
2023-06-15 10:10             ` Robin Dapp
2023-06-15 11:12               ` Richard Biener
     [not found]   ` <2023061516473052116877@rivai.ai>
2023-06-15  8:56     ` juzhe.zhong

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=93123844-a2a8-90ab-d47a-6f859fb3a8d6@gmail.com \
    --to=rdapp.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=krebbel@linux.ibm.com \
    --cc=linkw@linux.ibm.com \
    --cc=rguenther@suse.de \
    --cc=richard.sandiford@arm.com \
    --cc=uweigand@de.ibm.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).