Hi Tsukasa:

LGTM, and did you mind adding Signed-off-by to your patch and resending again?
I think this patch is small enough and the copyright process should
not be a blocker for this patch :)

See also: https://gcc.gnu.org/dco.html


On Sun, Apr 24, 2022 at 1:25 PM Tsukasa OI <research_tra...@irq.a4lg.com> wrote:
>
> **note**
>
> My copyright assignment to FSF is not yet started (will start just after
> sending this patch).  Please take care of the assignment status.
>
>
>
> This patch fixes RISC-V's canonical extension order...
> from: "J" -> "K"
> to  : "K" -> "J"
> as per the RISC-V ISA Manual draft-20210402-1271737 or later.
>
> This bug in the GCC is currently harmless because neither J nor
> Zj* extensions are implemented.  Intention of this commit is for future-
> proofness.
>
> This patch corresponds following patch for GNU Binutils:
> <https://sourceware.org/pipermail/binutils/2022-March/120277.html>
> [My copyright assignment is done on GNU Binutils]
>
> References:
> <https://github.com/riscv/riscv-isa-manual/commit/1271737463c04cacd98320d820a38f66d1c87dae>
> <https://github.com/riscv/riscv-isa-manual/releases/tag/draft-20210402-1271737>
>
>
>
>
> Tsukasa OI (1):
>   RISC-V: Fix canonical extension order (K and J)
>
>  gcc/common/config/riscv/riscv-common.cc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> base-commit: ab54f6007c79711fc2192098d4ccc3c24e95f3e6
> --
> 2.32.0
>

Reply via email to