public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Waterman <andrew@sifive.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	Nelson Chu <nelson.chu@sifive.com>,
	 Jim Wilson <jim.wilson.gcc@gmail.com>,
	Binutils <binutils@sourceware.org>
Subject: Re: Ping: [PATCH v2] RISC-V: correct FCVT.Q.L[U]
Date: Mon, 28 Mar 2022 13:46:13 -0700	[thread overview]
Message-ID: <CA++6G0A3SyFfmGwk6GXGLzycEuMF_WqpH08uTyaQ1P7m9Y6EZw@mail.gmail.com> (raw)
In-Reply-To: <808fd1e0-8993-66d9-e5aa-129e7916790a@suse.com>

Approved.  The old mapping is harmless, but the new mapping honors the
recommendation in the ISA spec for instructions that don't round.
I'll also add the corresponding note in the ISA spec for these
instructions.

On Mon, Mar 28, 2022 at 1:52 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 04.03.2022 13:41, Jan Beulich via Binutils wrote:
> > While the spec isn't explicit about this, it pointing out the similarity
> > with the D extension ought to extend to the ignoring of a meaningless
> > rounding mode: "Note FCVT.D.W[U] always produces an exact result and is
> > unaffected by rounding mode." Hence the chosen encodings also ought to
> > match.
> >
> > Note that to avoid breaking existing code the forms with a 3rd operand
> > are not removed, which means there continues to be a difference to
> > FCVT.D.W[U].
>
> I'd prefer to not commit such without arch maintainer approval; I guess
> I'll give it another week and the will assume the absence of comments to
> mean consent.
>
> Thanks, Jan
>
> > ---
> > Oddly enough there's looks to be no testing of the Q (or D/F) extension
> > beyond what was recently added for Zqinx (Zdinx/Zfinx).
> > ---
> > v2: Re-base.
> >
> > --- a/gas/testsuite/gas/riscv/zqinx.d
> > +++ b/gas/testsuite/gas/riscv/zqinx.d
> > @@ -28,8 +28,8 @@ Disassembly of section .text:
> >  [    ]+[0-9a-f]+:[   ]+46158553[     ]+fcvt.q.d[     ]+a0,a1
> >  [    ]+[0-9a-f]+:[   ]+d6058553[     ]+fcvt.q.w[     ]+a0,a1
> >  [    ]+[0-9a-f]+:[   ]+d6158553[     ]+fcvt.q.wu[    ]+a0,a1
> > -[    ]+[0-9a-f]+:[   ]+d625f553[     ]+fcvt.q.l[     ]+a0,a1
> > -[    ]+[0-9a-f]+:[   ]+d635f553[     ]+fcvt.q.lu[    ]+a0,a1
> > +[    ]+[0-9a-f]+:[   ]+d6258553[     ]+fcvt.q.l[     ]+a0,a1
> > +[    ]+[0-9a-f]+:[   ]+d6358553[     ]+fcvt.q.lu[    ]+a0,a1
> >  [    ]+[0-9a-f]+:[   ]+26c58553[     ]+fsgnj.q[      ]+a0,a1,a2
> >  [    ]+[0-9a-f]+:[   ]+26c59553[     ]+fsgnjn.q[     ]+a0,a1,a2
> >  [    ]+[0-9a-f]+:[   ]+26c5a553[     ]+fsgnjx.q[     ]+a0,a1,a2
> > --- a/opcodes/riscv-opc.c
> > +++ b/opcodes/riscv-opc.c
> > @@ -763,9 +763,9 @@ const struct riscv_opcode riscv_opcodes[
> >  {"fcvt.l.q",  64, INSN_CLASS_Q_OR_ZQINX,   "d,S,m",     MATCH_FCVT_L_Q, MASK_FCVT_L_Q, match_opcode, 0 },
> >  {"fcvt.lu.q", 64, INSN_CLASS_Q_OR_ZQINX,   "d,S",       MATCH_FCVT_LU_Q|MASK_RM, MASK_FCVT_LU_Q|MASK_RM, match_opcode, 0 },
> >  {"fcvt.lu.q", 64, INSN_CLASS_Q_OR_ZQINX,   "d,S,m",     MATCH_FCVT_LU_Q, MASK_FCVT_LU_Q, match_opcode, 0 },
> > -{"fcvt.q.l",  64, INSN_CLASS_Q_OR_ZQINX,   "D,s",       MATCH_FCVT_Q_L|MASK_RM, MASK_FCVT_Q_L|MASK_RM, match_opcode, 0 },
> > +{"fcvt.q.l",  64, INSN_CLASS_Q_OR_ZQINX,   "D,s",       MATCH_FCVT_Q_L, MASK_FCVT_Q_L|MASK_RM, match_opcode, 0 },
> >  {"fcvt.q.l",  64, INSN_CLASS_Q_OR_ZQINX,   "D,s,m",     MATCH_FCVT_Q_L, MASK_FCVT_Q_L, match_opcode, 0 },
> > -{"fcvt.q.lu", 64, INSN_CLASS_Q_OR_ZQINX,   "D,s",       MATCH_FCVT_Q_LU|MASK_RM, MASK_FCVT_Q_LU|MASK_RM, match_opcode, 0 },
> > +{"fcvt.q.lu", 64, INSN_CLASS_Q_OR_ZQINX,   "D,s",       MATCH_FCVT_Q_LU, MASK_FCVT_Q_LU|MASK_RM, match_opcode, 0 },
> >  {"fcvt.q.lu", 64, INSN_CLASS_Q_OR_ZQINX,   "D,s,m",     MATCH_FCVT_Q_LU, MASK_FCVT_Q_LU, match_opcode, 0 },
> >
> >  /* Compressed instructions.  */
> >
>

      reply	other threads:[~2022-03-28 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 12:41 Jan Beulich
2022-03-28  8:52 ` Ping: " Jan Beulich
2022-03-28 20:46   ` Andrew Waterman [this message]

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=CA++6G0A3SyFfmGwk6GXGLzycEuMF_WqpH08uTyaQ1P7m9Y6EZw@mail.gmail.com \
    --to=andrew@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=nelson.chu@sifive.com \
    --cc=palmer@dabbelt.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).