From: 钟居哲 <juzhe.zhong@rivai.ai>
To: rdapp.gcc <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, kito.cheng <kito.cheng@gmail.com>,
"Jeff Law" <jeffreyalaw@gmail.com>
Cc: rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Add popcount fallback expander.
Date: Wed, 18 Oct 2023 22:08:04 +0800 [thread overview]
Message-ID: <8BAE2A4E8933C76D+2023101822080396248451@rivai.ai> (raw)
In-Reply-To: <6eaff1b7-8c7d-4452-a4f5-6129709866be@gmail.com>
Could you by the way add this mention this PR:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111791
Add the test of this PR ?
juzhe.zhong@rivai.ai
From: Robin Dapp
Date: 2023-10-18 21:51
To: juzhe.zhong@rivai.ai; gcc-patches; palmer; kito.cheng; jeffreyalaw
CC: rdapp.gcc
Subject: Re: [PATCH] RISC-V: Add popcount fallback expander.
I didn't push this yet because it would have introduced an UNRESOLVED that
my summary script didn't catch. Normally I go with just contrib/test_summary
but that only filters out FAIL and XPASS. I should really be using
compare_testsuite_log.py from riscv-gnu-toolchain/scripts.
It was caused by a typo:
-/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 1 "slp" } } */
+/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 1 "slp2" } } */
Regards
Robin
next prev parent reply other threads:[~2023-10-18 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:20 Robin Dapp
2023-10-18 9:28 ` juzhe.zhong
2023-10-18 9:32 ` Robin Dapp
2023-10-18 11:43 ` Robin Dapp
2023-10-18 11:48 ` juzhe.zhong
2023-10-18 12:22 ` juzhe.zhong
2023-10-18 13:51 ` Robin Dapp
2023-10-18 14:08 ` 钟居哲 [this message]
2023-10-18 20:25 ` Robin Dapp
[not found] ` <202310181728104086621@rivai.ai>
2023-10-18 9:30 ` juzhe.zhong
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=8BAE2A4E8933C76D+2023101822080396248451@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=rdapp.gcc@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).