From: "Lehua Ding" <lehua.ding@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>, "pan2.li" <pan2.li@intel.com>,
"Jeff Law" <jeffreyalaw@gmail.com>, 钟居哲 <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
"yanzhang.wang" <yanzhang.wang@intel.com>,
"kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Add tuple vector mode psABI checking and simplify code
Date: Tue, 20 Jun 2023 21:13:27 +0800 [thread overview]
Message-ID: <tencent_148C0CF76DE324382D565BA7@qq.com> (raw)
In-Reply-To: <2cea1e64-6413-ca36-f839-b8728b710dae@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
> Actually they are already in for a bit :)
> 51795b910737 (Robin Dapp 2023-06-01 14:18:57 +0200 1) /* { dg-do compile } */
>I thought something is special about them that they somehow didn't run
> on your machine or so.
The time I just said is your commit time from this link
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=51795b91073798c718df6fafb01303861641a5af.
authorRobin Dapp <rdapp@ventanamicro.com>
Thu, 1 Jun 2023 12:18:57 +0000 (14:18 +0200)
committerRobin Dapp <rdapp@ventanamicro.com>
Mon, 19 Jun 2023 07:58:35 +0000 (09:58 +0200)
And I just ran these cases locally and also reported an error.
Are there some good ways to avoid this here?
Best,
Lehua
next prev parent reply other threads:[~2023-06-20 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 11:41 Lehua Ding
2023-06-18 13:16 ` 钟居哲
2023-06-19 18:03 ` Jeff Law
2023-06-20 1:16 ` Li, Pan2
2023-06-20 12:10 ` Robin Dapp
2023-06-20 12:58 ` Lehua Ding
2023-06-20 13:01 ` Robin Dapp
2023-06-20 13:13 ` Lehua Ding [this message]
2023-06-20 13:44 ` Lehua Ding
2023-06-20 13:50 ` Robin Dapp
2023-06-20 14:03 ` Robin Dapp
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=tencent_148C0CF76DE324382D565BA7@qq.com \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=pan2.li@intel.com \
--cc=rdapp.gcc@gmail.com \
--cc=yanzhang.wang@intel.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).