public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-721] testsuite/rs6000: Adjust gcc.target/powerpc/pr78604.c [PR105706] Date: Tue, 24 May 2022 06:09:02 +0000 (GMT) [thread overview] Message-ID: <20220524060902.B1014385625E@sourceware.org> (raw) https://gcc.gnu.org/g:8fa8bca9f53fcfdedc2b4fa55093dbd1ab7abbd1 commit r13-721-g8fa8bca9f53fcfdedc2b4fa55093dbd1ab7abbd1 Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue May 24 01:00:40 2022 -0500 testsuite/rs6000: Adjust gcc.target/powerpc/pr78604.c [PR105706] Commit r13-707 adjusts the below gimple: iftmp.7_4 = _1 < _2 ? val2_7(D) : val1_8(D); to _3 = _1 >= _2; iftmp.7_4 = _3 ? val1_8(D) : val2_7(D); and result in one more vect_model_simple_cost dumping for each function. Need to adjust the match count accordingly. PR testsuite/105706 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr78604.c: Adjust. Diff: --- gcc/testsuite/gcc.target/powerpc/pr78604.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/powerpc/pr78604.c b/gcc/testsuite/gcc.target/powerpc/pr78604.c index 35bfdb35412..7a371af8c28 100644 --- a/gcc/testsuite/gcc.target/powerpc/pr78604.c +++ b/gcc/testsuite/gcc.target/powerpc/pr78604.c @@ -109,4 +109,6 @@ uns_gte (UNS_TYPE val1, UNS_TYPE val2) /* { dg-final { scan-assembler-times {\mvcmpgtsd\M} 4 } } */ /* { dg-final { scan-assembler-times {\mvcmpgtud\M} 4 } } */ /* { dg-final { scan-assembler-not {\mvcmpequd\M} } } */ -/* { dg-final { scan-tree-dump-times "vect_model_simple_cost" 8 "vect" } } */ +/* For each function, one is for the comparison statement and the other + is for the condition statement which consumes the compared result. */ +/* { dg-final { scan-tree-dump-times "vect_model_simple_cost" 16 "vect" } } */
reply other threads:[~2022-05-24 6:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220524060902.B1014385625E@sourceware.org \ --to=linkw@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).