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/106516] New test case gcc.dg/pr104992.c fails on power 10 Date: Thu, 04 Aug 2022 06:24:50 +0000 [thread overview] Message-ID: <bug-106516-4-ymL2zaG6gv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106516-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |linkw at gcc dot gnu.org Last reconfirmed| |2022-08-04 Status|UNCONFIRMED |NEW --- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> --- Confirmed, this is a test issue, power10 and up specific. The difference comes from the function thud, it aims to test the pattern works for vector type. Power10 starts to support the insn vmodsw for vector integer mod. So it gets: vector(4) int thud (vector(4) int x, vector(4) int y) _1 = x_3(D) % y_4(D); _2 = _1 == { 0, 0, 0, 0 }; instead of <bb 2> [local count: 1073741824]: _7 = BIT_FIELD_REF <x_3(D), 32, 0>; _8 = BIT_FIELD_REF <y_4(D), 32, 0>; _9 = _7 % _8; _10 = BIT_FIELD_REF <x_3(D), 32, 32>; _11 = BIT_FIELD_REF <y_4(D), 32, 32>; _12 = _10 % _11; _13 = BIT_FIELD_REF <x_3(D), 32, 64>; _14 = BIT_FIELD_REF <y_4(D), 32, 64>; _15 = _13 % _14; _16 = BIT_FIELD_REF <x_3(D), 32, 96>; _17 = BIT_FIELD_REF <y_4(D), 32, 96>; _18 = _16 % _17; _1 = {_9, _12, _15, _18}; _2 = _1 == { 0, 0, 0, 0 }; We can adjust the test case to expect 6 times "%" on target power10_ok specially, but I wonder if we also find this fail on some other targets which supports vector mod, if so, one overall complete guard would be better.
next prev parent reply other threads:[~2022-08-04 6:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-03 15:53 [Bug testsuite/106516] New: New test case gcc.dg/pr104992.c fails seurer at gcc dot gnu.org 2022-08-03 15:59 ` [Bug testsuite/106516] New test case gcc.dg/pr104992.c fails on power 10 seurer at gcc dot gnu.org 2022-08-04 6:24 ` linkw at gcc dot gnu.org [this message] 2022-08-24 2:25 ` linkw at gcc dot gnu.org 2022-08-24 18:43 ` bergner at gcc dot gnu.org 2022-09-30 12:18 ` cvs-commit at gcc dot gnu.org 2022-09-30 12:28 ` linkw at gcc dot gnu.org 2024-01-20 17:21 ` 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-106516-4-ymL2zaG6gv@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: 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).