From: Jan Beulich <jbeulich@suse.com>
To: im Kiva <libkernelpanic@gmail.com>, Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [RISCV] [GNU AS] Possible `vmsge{u}.vx` instruction lowering bug?
Date: Tue, 29 Aug 2023 09:43:21 +0200 [thread overview]
Message-ID: <dcbade83-6d7f-be2b-3037-bf3ee29db8a4@suse.com> (raw)
In-Reply-To: <CA+fTAJqPu6Aszt9FtqGXw8JOC6UY56k+BwOZw_VjZ7RpA2Wmyw@mail.gmail.com>
On 29.08.2023 08:52, im Kiva via Binutils wrote:
> Hi maintainers,
>
> I discovered that GNU Assembler (as) lowers `vmsge.vx` and `vmsgeu.vx` (pseudo
> instructions from RISC-V Vector Extension [1]) when the destination
> register is v0 as follows:
>
> vmsge{u}.vx v0, v4, a0, v0.t, v2
>
> will be expanded to:
>
> vmslt{u}.vx v2, v4, a0, v0.t
> vmandn.mm v0, v0, v2
>
> You can inspect the lowering result with Godbolt [2].
> However, according to the Vector specification [1] page 52. The "desugared"
> `vmslt{u}.vx` is not masked:
>
>> masked va >= x, vd == v0
>> pseudoinstruction: vmsge{u}.vx vd, va, x, v0.t, vt
>> expansion: vmslt{u}.vx vt, va, x; vmandn.mm vd, vd, vt
>
> So the spec-expected result of the example above should be:
> vmslt{u}.vx v2, v4, a0 <-- no v0.t here
> vmandn.mm v0, v0, v2
>
> I thus submitted a patch to the LLVM [3], and it was accepted recently.
>
> I am wondering if binutils considers it a bug, or if it is just intentional
> because of some historical and compatibility reasons.
I think this wants fixing alike in binutils: From looking at vector_macro(),
it appears that emitting the masked form is merely an accident resulting
from the inverted encoding of "masking". In particular, if masking was
indeed meant, I expect code there would be
if (vd == vm)
{
macro_build (NULL, "vmslt.vx", "Vd,Vt,sVm", vtemp, vs2, vs1, vm);
macro_build (NULL, "vmandnot.mm", "Vd,Vt,Vs", vd, vm, vtemp);
}
else
...
much like it is a few lines down from there. (Apparently the "else" path
omitted above is similarly affected.)
Jan
next prev parent reply other threads:[~2023-08-29 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:52 im Kiva
2023-08-29 7:43 ` Jan Beulich [this message]
2023-08-29 7:59 ` Nelson Chu
2023-08-29 8:52 ` Jan Beulich
2023-08-30 2:51 ` Nelson Chu
2023-08-30 5:50 ` Jan Beulich
2023-09-01 6:37 ` Kiva Oyama
2023-09-01 8:03 ` Nelson Chu
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=dcbade83-6d7f-be2b-3037-bf3ee29db8a4@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=libkernelpanic@gmail.com \
--cc=nelson@rivosinc.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).