From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com,
jim.wilson.gcc@gmail.com, palmer@dabbelt.com, andrew@sifive.com,
christoph.muellner@vrull.eu
Subject: Re: [PATCH 0/5] RISC-V: Relax the -march string for accept any order
Date: Tue, 16 Jan 2024 07:33:06 -0700 [thread overview]
Message-ID: <5230d058-9f3b-492d-bf5b-144fc79755e2@gmail.com> (raw)
In-Reply-To: <CALLt3Tgn5SpveYKW=yxDag+uZi3LTsM40ZGzfgPFJi9Fr+fV9g@mail.gmail.com>
On 1/9/24 17:58, Kito Cheng wrote:
> Oops, I should leave more context here:
>
> Actually we discussed that years ago, and most people agree with that,
> but I guess we are just missing that, and also the ISA string isn't so
> terribly long yet at that moment, however...the number of extensions are
> growth so fast in last year, so I think it's time to moving this forward.
>
> Also we (SiFive) will send patches for clang/LLVM to relax that as well :)
>
> https://github.com/riscv-non-isa/riscv-toolchain-conventions/pull/14
> <https://github.com/riscv-non-isa/riscv-toolchain-conventions/pull/14>
Then let's go forward. It seems like as good a time as any with gcc-14
and llvm-18 both right around the corner.
jeff
next prev parent reply other threads:[~2024-01-16 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 13:47 Kito Cheng
2024-01-08 13:47 ` [PATCH 1/5] RISC-V: Extract part parsing base ISA logic into a standalone function [NFC] Kito Cheng
2024-01-08 13:47 ` [PATCH 2/5] RISC-V: Relax the -march string for accept any order Kito Cheng
2024-01-08 13:47 ` [PATCH 3/5] RISC-V: Remove unused function in riscv_subset_list [NFC] Kito Cheng
2024-01-08 13:47 ` [PATCH 4/5] RISC-V: Update testsuite due to -march string relaxation Kito Cheng
2024-01-08 13:47 ` [PATCH 5/5] RISC-V: Document the syntax of -march Kito Cheng
2024-01-09 18:31 ` [PATCH 0/5] RISC-V: Relax the -march string for accept any order Jeff Law
2024-01-10 0:58 ` Kito Cheng
2024-01-10 1:38 ` Fangrui Song
2024-01-16 14:33 ` Jeff Law [this message]
2024-01-19 7:20 ` Kito Cheng
2024-01-19 9:36 juzhe.zhong
2024-01-19 9:39 ` Kito Cheng
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=5230d058-9f3b-492d-bf5b-144fc79755e2@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=andrew@sifive.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@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).