public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 30 Sep 2022 12:18:27 +0000	[thread overview]
Message-ID: <bug-106516-4-qEgPWp7YK6@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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:c28957176dc0adff6e4b8fcbe6b91f5b82900563

commit r13-2983-gc28957176dc0adff6e4b8fcbe6b91f5b82900563
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Fri Sep 30 07:16:36 2022 -0500

    rs6000/test: Adjust pr104992.c with vect_int_mod [PR106516]

    As PR106516 shows, we can get unexpected gimple outputs for
    function thud on some target which supports modulus operation
    for vector int.  This patch introduces one effective target
    vect_int_mod for it, then adjusts the test case with it.

            PR testsuite/106516

    gcc/testsuite/ChangeLog:

            * gcc.dg/pr104992.c: Adjust with vect_int_mod.
            * lib/target-supports.exp (check_effective_target_vect_int_mod):
New
            effective target.

  parent reply	other threads:[~2022-09-30 12:18 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
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 [this message]
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-qEgPWp7YK6@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).