From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: jeffreyalaw <jeffreyalaw@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Fine tune gather load RA constraint
Date: Mon, 20 Mar 2023 08:49:21 +0800 [thread overview]
Message-ID: <CDEBC993D64FD9A8+202303200849207761080@rivai.ai> (raw)
In-Reply-To: <22dd21a2-f1d8-6826-b0ba-69104c1d7d83@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
It's ok to defer them GCC-14. I will keep testing and fix bugs during these 2 months.
I won't support any more feature or optimizations until GCC-14 is open.
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2023-03-20 00:55
To: juzhe.zhong@rivai.ai; gcc-patches
CC: kito.cheng
Subject: Re: [PATCH] RISC-V: Fine tune gather load RA constraint
On 3/15/23 00:52, juzhe.zhong@rivai.ai wrote:
> Hi, Jeff. I really hope the current "refine tune RA constraint" patches
> can be merged into GCC-13.
> These patches are just making RA constraint to be consistent with RVV
> ISA after I double checked RVV ISA.
> These RA constraints changing is very safe.They may be very safe, but we're *way* past the point where we should be
making this kind of change. When I agreed to not object to including
the RVV builtins in gcc-13, I never imagined we'd still be making
changes to that code in March. My bad for not getting clarification on
how much work remained to be done.
Jeff
next prev parent reply other threads:[~2023-03-20 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 8:28 juzhe.zhong
2023-03-14 18:08 ` Jeff Law
2023-03-15 6:52 ` juzhe.zhong
2023-03-19 16:55 ` Jeff Law
2023-03-20 0:49 ` juzhe.zhong [this message]
2023-04-21 20:36 ` Jeff Law
2023-04-24 3:05 ` juzhe.zhong
2023-04-26 4:21 ` 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=CDEBC993D64FD9A8+202303200849207761080@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.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).