On Thu, 03 Nov 2022 12:11:31 PDT (-0700), christoph.muell...@vrull.eu wrote:
On Wed, Nov 2, 2022 at 7:12 PM Palmer Dabbelt wrote:
On Wed, 02 Nov 2022 10:19:15 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
> Could you add some test cases?
Also documentation, and ideally some sort of spec for wha
On Wed, Nov 2, 2022 at 7:12 PM Palmer Dabbelt wrote:
>
> On Wed, 02 Nov 2022 10:19:15 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
> > Could you add some test cases?
>
> Also documentation, and ideally some sort of spec for what this should
> do so we can maintain compatibility with LLVM as well as
On Wed, 02 Nov 2022 10:19:15 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
Could you add some test cases?
Also documentation, and ideally some sort of spec for what this should
do so we can maintain compatibility with LLVM as well as we can.
IIUC this also allows for profiles in the arch funct
Could you add some test cases?
---
Parsing logic is kind of too adhoc, I would prefer using something
like the following code to prevent magic pointer arithmetic like p+6:
something like this:
Table of all profile names = {"RVA20U64", riscv_profile::RVA20U64, ...}
const char *rva20u64[] = {"m"
Add two new function to handle profile input,
"parse_profile" will check if a input into -march is
legal, if it is then "handle_profile" will check the
profile's type[I/M/A], year[20/22] and mode[U/S/M],
set different extensions combine, just deal mandatory
part currently.
gcc/ChangeLog:
Supports RISC-V profiles[1] in -march option, add minimal extension name
supports.
Default input set the profile is before other formal extensions.
Test with -march=RV[I/M/A]2[0/2][U/M/S][64/32]+otherextensions.
[1]https://github.com/riscv/riscv-profiles/blob/main/profiles.adoc
jiawei (2):
