public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/105706] [13 regression] gcc.target/powerpc/pr78604.c fails after r13-707-g68e0063397ba82
Date: Tue, 24 May 2022 02:46:10 +0000 [thread overview]
Message-ID: <bug-105706-4-L95pIjrGYr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105706
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linkw at gcc dot gnu.org
Last reconfirmed| |2022-05-24
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to seurer from comment #0)
> g:68e0063397ba820e71adc220b2da0581dce29ffa, r13-707-g68e0063397ba82
> make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr78604.c"
> FAIL: gcc.target/powerpc/pr78604.c scan-tree-dump-times vect
> "vect_model_simple_cost" 8
> # of expected passes 4
> # of unexpected failures 1
>
>
> Does this test need to be adjusted, too?
>
Yes. The related commit mainly adjust the below gimple:
iftmp.7_4 = _1 < _2 ? val2_7(D) : val1_8(D);
into
_3 = _1 >= _2;
iftmp.7_4 = _3 ? val1_8(D) : val2_7(D);
So for each function it has two statements (comparison and condition) calling
vect_model_simple_cost instead of one (condition). By checking the history, the
case was updated with r8-731, which meant to verify if vectorized COND_EXPRs
calling vect_model_simple_cost.
One simple fix is to adjust the match count to 16.
next prev parent reply other threads:[~2022-05-24 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:13 [Bug testsuite/105706] New: " seurer at gcc dot gnu.org
2022-05-24 2:46 ` linkw at gcc dot gnu.org [this message]
2022-05-24 6:04 ` [Bug testsuite/105706] " linkw at gcc dot gnu.org
2022-05-24 6:09 ` cvs-commit at gcc dot gnu.org
2022-05-24 6:22 ` linkw at gcc dot gnu.org
2022-10-31 19:19 ` pinskia at gcc dot gnu.org
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=bug-105706-4-L95pIjrGYr@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).