From: "Li, Pan2" <pan2.li@intel.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: jeffreyalaw <jeffreyalaw@gmail.com>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>,
kito.cheng <kito.cheng@gmail.com>
Subject: RE: [PATCH v1] RISC-V: Align the predictor style for define_insn_and_split
Date: Wed, 14 Jun 2023 06:51:19 +0000 [thread overview]
Message-ID: <MW5PR11MB590807FD06E46207C0847837A95AA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7ac0a5c9-0d8f-2a4a-d032-7b51e5c340ed@gmail.com>
> Any numbers on this Pan? How many cores do you use for running the testsuite?
Sorry for missing this part. It takes about 4-6 minutes with spike and 16 cores.
Pan
-----Original Message-----
From: Robin Dapp <rdapp.gcc@gmail.com>
Sent: Wednesday, June 14, 2023 2:47 PM
To: Li, Pan2 <pan2.li@intel.com>; juzhe.zhong@rivai.ai; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rdapp.gcc@gmail.com; jeffreyalaw <jeffreyalaw@gmail.com>; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH v1] RISC-V: Align the predictor style for define_insn_and_split
> I don't have a proper sim environment setup yet. How long does the testsuite take
> with spike? Have you tried qemu as well?
Any numbers on this Pan? How many cores do you use for running the testsuite?
Regards
Robin
next prev parent reply other threads:[~2023-06-14 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 2:15 pan2.li
2023-06-14 2:31 ` juzhe.zhong
2023-06-14 6:00 ` Li, Pan2
2023-06-14 6:09 ` Robin Dapp
2023-06-14 6:30 ` juzhe.zhong
2023-06-14 6:36 ` Li, Pan2
2023-06-14 6:47 ` Robin Dapp
2023-06-14 6:51 ` Li, Pan2 [this message]
2023-06-14 6:52 ` Robin Dapp
2023-06-14 7:01 ` juzhe.zhong
2023-06-14 7:02 ` Robin Dapp
2023-06-14 7:06 ` Li, Pan2
2023-06-14 18:51 ` Jeff Law
2023-06-15 1:07 ` Li, Pan2
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=MW5PR11MB590807FD06E46207C0847837A95AA@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.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).