From: Robin Dapp <rdapp@linux.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, jakub@redhat.com
Subject: Re: VN, len_store and endianness
Date: Tue, 27 Sep 2022 15:59:06 +0200 [thread overview]
Message-ID: <11b57f53-499a-bed8-97cd-95f7c1a0f074@linux.ibm.com> (raw)
In-Reply-To: <CAFiYyc09+ZJLVfZUeRUXZyBgmDamtP9r8rWtKOwmU4zQWYG3ug@mail.gmail.com>
> Yes, because the native_interpret always starts at offset zero
> (we can't easily feed in a "shifted" RHS). So what I assumed is
> that IFN_LEN_STORE always stores elements [0, len + adj].
Hmm, but this assumption is not violated here or am I missing something?
It's not like we're storing [vec_size - (len + adj) - 1, vec_size - 1]
but indeed [0, len + adj]. Just the access to the buffer later is
reversed which it should not be.
next prev parent reply other threads:[~2022-09-27 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 14:21 Robin Dapp
2022-09-27 8:39 ` Richard Biener
2022-09-27 13:19 ` Robin Dapp
2022-09-27 13:49 ` Richard Biener
2022-09-27 13:59 ` Robin Dapp [this message]
2022-09-29 7:32 ` Richard Biener
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=11b57f53-499a-bed8-97cd-95f7c1a0f074@linux.ibm.com \
--to=rdapp@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@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).