From: Jan Beulich <jbeulich@suse.com>
To: Christoph Muellner <christoph.muellner@vrull.eu>
Cc: binutils@sourceware.org, Nelson Chu <nelson@rivosinc.com>,
Andrew Waterman <andrew@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kito Cheng <kito.cheng@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>,
Tsukasa OI <research_trasio@irq.a4lg.com>
Subject: Re: [RFC PATCH v4 2/2] RISC-V: Add support for the Zfa extension
Date: Fri, 7 Apr 2023 11:02:07 +0200 [thread overview]
Message-ID: <2c0f8c70-9482-ae19-32a7-bbd0aec9a0c4@suse.com> (raw)
In-Reply-To: <20230330175438.107102-3-christoph.muellner@vrull.eu>
On 30.03.2023 19:54, Christoph Muellner wrote:
> --- a/gas/doc/c-riscv.texi
> +++ b/gas/doc/c-riscv.texi
> @@ -18,6 +18,7 @@
> * RISC-V-Options:: RISC-V Options
> * RISC-V-Directives:: RISC-V Directives
> * RISC-V-Modifiers:: RISC-V Assembler Modifiers
> +* RISC-V-Modifiers:: RISC-V Floating Point
If I'm not mistaken the left side here is a copy-and-paste mistake, but
then I also wonder whether ...
> @@ -382,6 +383,46 @@ The pseudo la.tls.gd instruction can be expended to
>
> @end table
>
> +@node RISC-V-Format
... this isn't kind of, too (and it's e.g. RISC-V-Floating-Point that's
meant here, better matching ...
> +@section RISC-V Floating-point
... this).
Jan
next prev parent reply other threads:[~2023-04-07 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 17:54 [RFC PATCH v4 0/2] " Christoph Muellner
2023-03-30 17:54 ` [RFC PATCH v4 1/2] RISC-V: Allocate "various" operand type Christoph Muellner
2023-03-31 2:20 ` Nelson Chu
2023-03-31 8:30 ` Philipp Tomsich
2023-03-30 17:54 ` [RFC PATCH v4 2/2] RISC-V: Add support for the Zfa extension Christoph Muellner
2023-04-07 9:02 ` Jan Beulich [this message]
2023-04-13 13:37 ` Christoph Müllner
2023-04-12 6:53 ` Nelson Chu
2023-04-13 13:39 ` Christoph Müllner
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=2c0f8c70-9482-ae19-32a7-bbd0aec9a0c4@suse.com \
--to=jbeulich@suse.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=research_trasio@irq.a4lg.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).