public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner 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: Wed, 24 Aug 2022 18:43:38 +0000	[thread overview]
Message-ID: <bug-106516-4-LpPqZShD4A@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 #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #7)
> In this patch, I mainly
> followed the existing practice vect_int_mult (there are also some similar
> effective targets describing target vector support capability). With this
> way, if some other arches support this in future, target owners need to add
> their own conditions.

Yes, and those target maintainers will notice when they add the HW support and
then see this test case FAIL, just like we did on P10.

  parent reply	other threads:[~2022-08-24 18:43 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 [this message]
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-LpPqZShD4A@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).