public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	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 v3 1/3] RISC-V: Add stub support for existing extensions (privileged)
Date: Tue, 29 Aug 2023 07:41:37 -0600	[thread overview]
Message-ID: <541acb7a-8489-0808-288a-cdf16a247eb5@gmail.com> (raw)
In-Reply-To: <19d23833ccf469122fa93a35b7f1c369012034b2.1693280368.git.research_trasio@irq.a4lg.com>



On 8/28/23 21:39, Tsukasa OI wrote:
> From: Tsukasa OI <research_trasio@irq.a4lg.com>
> 
> After commit c283c4774d1c ("RISC-V: Throw compilation error for unknown
> extensions") changed how do we handle unknown extensions, we have no
> guarantee that we can share the same architectural string with Binutils
> (specifically, the assembler).
> 
> To avoid compilation errors on shared Assembler-C/C++ projects or programs
> with inline assembler, GCC should support almost all extensions that
> Binutils support, even if the GCC itself does not touch a thing.
> 
> As a start, this commit adds stub supported *privileged* extensions to
> riscv_ext_version_table and its implications to riscv_implied_info
> (all information is copied from Binutils' bfd/elfxx-riscv.c).
> 
> gcc/ChangeLog:
> 
> 	* common/config/riscv/riscv-common.cc
> 	(riscv_implied_info): Add implications from privileged extensions.
> 	(riscv_ext_version_table): Add stub support for all privileged
> 	extensions supported by Binutils.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.target/riscv/predef-29.c: New test for a stub privileged
> 	extension 'Smstateen' with some implications.
OK
jeff

  reply	other threads:[~2023-08-29 13:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  2:57 [PATCH 0/3] RISC-V: Add stub support for existing extensions 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   ` [PATCH v2 0/3] RISC-V: Add stub support for existing extensions Tsukasa OI
2023-08-29  3:39   ` [PATCH v3 " 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 [this message]
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=541acb7a-8489-0808-288a-cdf16a247eb5@gmail.com \
    --to=jeffreyalaw@gmail.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 \
    --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).