From: Robin Dapp <rdapp.gcc@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rdapp.gcc@gmail.com, jeffreyalaw <jeffreyalaw@gmail.com>,
rguenther <rguenther@suse.de>
Subject: Re: [PATCH] testsuite/vect: Make check more accurate.
Date: Tue, 7 Nov 2023 09:34:20 +0100 [thread overview]
Message-ID: <0afce0b7-157f-4357-a079-185ac423fa4b@gmail.com> (raw)
In-Reply-To: <4EB30EB6CA1D3331+2023110716310417927719@rivai.ai>
Sorry, didn't reply-all:
> /* { dg-final { scan-tree-dump-times "optimizing condition reduction with FOLD_EXTRACT_LAST" 4 "vect" { target { { vect_fold_extract_last } && { ! vect_pack_trunc } } } } } */
>
> This check should be removed. Previously, I added it since we didn't enable vect_pack_trunc test.
> But I think we don't need it any more. Your fix looks more reasonable.
Ah, good, will remove it before committing.
Regards
Robin
next prev parent reply other threads:[~2023-11-07 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 8:31 juzhe.zhong
2023-11-07 8:34 ` Robin Dapp [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 8:22 Robin Dapp
2023-11-07 8:28 ` Richard Biener
2023-11-09 20:00 ` Thomas Schwinge
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=0afce0b7-157f-4357-a079-185ac423fa4b@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=rguenther@suse.de \
/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).