From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2 0/3] RISC-V: Add stub support for existing extensions
Date: Mon, 14 Aug 2023 15:17:32 +0900 [thread overview]
Message-ID: <66f16e57-06ad-48ed-8240-c289922412bc@irq.a4lg.com> (raw)
In-Reply-To: <cover.1691993380.git.research_trasio@irq.a4lg.com>
Hi,
I'll explain a little more background.
A major case which this patch set will be required is when a developer
use inline assembly for instructions not yet natively supported by GCC
or will not be supported as intrinsics.
On such cases, GCC should at least accept corresponding extension via
-march (although there's a workaround using ".option" directives in the
inline assembly but that's tedious).
Thanks,
Tsukasa
On 2023/08/14 15:09, Tsukasa OI wrote:
> PATCH v1:
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627220.html>
>
>
> Changes: v1 -> v2 (only in PATCH 3/3)
> ======================================
>
> Removed: 'Zvkn' -> 'Zvknha' implication (not to cause test failure)
> Added: 'Zfa' -> 'F' implication (just I forgot to add in PATCH v1)
>
>
> Thanks,
> Tsukasa
>
>
>
>
> Tsukasa OI (3):
> RISC-V: Add stub support for existing extensions (privileged)
> RISC-V: Add stub support for existing extensions (vendor)
> RISC-V: Add stub support for existing extensions (unprivileged)
>
> gcc/common/config/riscv/riscv-common.cc | 44 ++++++++++++++++++++++
> gcc/testsuite/gcc.target/riscv/predef-29.c | 35 +++++++++++++++++
> gcc/testsuite/gcc.target/riscv/predef-30.c | 27 +++++++++++++
> gcc/testsuite/gcc.target/riscv/predef-31.c | 31 +++++++++++++++
> 4 files changed, 137 insertions(+)
> create mode 100644 gcc/testsuite/gcc.target/riscv/predef-29.c
> create mode 100644 gcc/testsuite/gcc.target/riscv/predef-30.c
> create mode 100644 gcc/testsuite/gcc.target/riscv/predef-31.c
>
>
> base-commit: 614052dd4ea083e086712809c754ffebd9361316
next prev parent reply other threads:[~2023-08-14 6:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 2:57 [PATCH " Tsukasa OI
2023-08-12 2:57 ` [PATCH 1/3] RISC-V: Add stub support for existing extensions (privileged) Tsukasa OI
2023-08-12 2:57 ` [PATCH 2/3] RISC-V: Add stub support for existing extensions (vendor) Tsukasa OI
2023-08-12 2:57 ` [PATCH 3/3] RISC-V: Add stub support for existing extensions (unprivileged) Tsukasa OI
2023-08-14 6:09 ` [PATCH v2 0/3] RISC-V: Add stub support for existing extensions Tsukasa OI
2023-08-14 6:09 ` [PATCH v2 1/3] RISC-V: Add stub support for existing extensions (privileged) Tsukasa OI
2023-08-14 6:09 ` [PATCH v2 2/3] RISC-V: Add stub support for existing extensions (vendor) Tsukasa OI
2023-08-14 6:09 ` [PATCH v2 3/3] RISC-V: Add stub support for existing extensions (unprivileged) Tsukasa OI
2023-08-29 1:42 ` Jeff Law
2023-08-29 3:14 ` Tsukasa OI
2023-08-14 6:17 ` Tsukasa OI [this message]
2023-08-29 3:39 ` [PATCH v3 0/3] RISC-V: Add stub support for existing extensions Tsukasa OI
2023-08-29 3:39 ` [PATCH v3 1/3] RISC-V: Add stub support for existing extensions (privileged) Tsukasa OI
2023-08-29 13:41 ` Jeff Law
2023-08-29 3:39 ` [PATCH v3 2/3] RISC-V: Add stub support for existing extensions (vendor) Tsukasa OI
2023-08-29 13:42 ` Jeff Law
2023-08-29 3:39 ` [PATCH v3 3/3] RISC-V: Add stub support for existing extensions (unprivileged) Tsukasa OI
2023-08-29 13:42 ` Jeff Law
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=66f16e57-06ad-48ed-8240-c289922412bc@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.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).