public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	Nelson Chu <nelson.chu@sifive.com>,
	Weiwei Li <liweiwei@iscas.ac.cn>
Cc: binutils@sourceware.org
Subject: [PATCH v2 0/1] RISC-V: QUICK fix on Li's Zhinx implementation
Date: Fri, 24 Jun 2022 11:59:03 +0900	[thread overview]
Message-ID: <cover.1656039500.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1654404125.git.research_trasio@irq.a4lg.com>

This is a backup plan if my main Zfinx fixes will not make it to
Binutils 2.39 and contains the most important fix (to most likely wrong
feature gate) to Li's Zhinx implementation.

Because of this, this is incompatible with my main patchset
("RISC-V: Combined floating point enhancements") which contains all of
Zfinx/Zhinx fixes.

v1:
<https://sourceware.org/pipermail/binutils/2022-June/121170.html>
CURRENT (GitHub):
<https://github.com/a4lg/binutils-gdb/tree/riscv-zhinx-quick-fix>


This is functionally equivalent to v1 but contains a minor change.

[CHANGES: v1 -> v2]
-   Change error message to enable i18n.
-   Removed original PATCH 1 because it is merged.
    <https://sourceware.org/pipermail/binutils/2022-June/121342.html>




Tsukasa OI (1):
  RISC-V: Fix requirement handling on Zhinx+{D,Q}

 bfd/elfxx-riscv.c                        | 30 ++++++++++++++++++++----
 gas/testsuite/gas/riscv/fp-zhinx-insns.d |  2 +-
 2 files changed, 26 insertions(+), 6 deletions(-)


base-commit: 54603ee2aeaf248220f0f440c322ff02e98cd403
-- 
2.34.1


  parent reply	other threads:[~2022-06-24  2:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  4:43 [PATCH 0/2] " Tsukasa OI
2022-06-05  4:43 ` [PATCH 1/2] RISC-V: Add 'H' to canonical extension ordering Tsukasa OI
2022-06-22 10:39   ` Nelson Chu
2022-06-22 11:08     ` Tsukasa OI
2022-06-05  4:43 ` [PATCH 2/2] RISC-V: Fix requirement handling on Zhinx+{D,Q} Tsukasa OI
2022-06-24  2:59 ` Tsukasa OI [this message]
2022-06-24  2:59   ` [PATCH v2 1/1] " Tsukasa OI
2022-06-24  3:51   ` [PATCH v3 0/2] RISC-V: QUICK fix on Li's Zhinx implementation Tsukasa OI
2022-06-24  3:51     ` [PATCH v3 1/2] RISC-V: Fix requirement handling on Zhinx+{D,Q} Tsukasa OI
2022-07-07  3:02       ` Kito Cheng
2022-07-07  4:25         ` Nelson Chu
2022-06-24  3:51     ` [PATCH v3 2/2] RISC-V: Reorder Zhinx extension Tsukasa OI

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=cover.1656039500.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=kito.cheng@sifive.com \
    --cc=liweiwei@iscas.ac.cn \
    --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).