public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110960] TestSatWidenMulPairwiseAdd in the Google Highway test suite fails when compiled with GCC 12 or later with the -mcpu=power9 option
Date: Fri, 08 Sep 2023 15:58:45 +0000 [thread overview]
Message-ID: <bug-110960-4-96SEBHKhZG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110960-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110960
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Mathieu Malaterre from comment #7)
> @rguenth You added `needs-bisection` keyword, but the example is quite
> small: 154 lines of code.
needs-bisection means to figure out which commit caused the regression.
That is different from needs-reduction keyword which says we need a reduction
still ...
next prev parent reply other threads:[~2023-09-08 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:14 [Bug target/110960] New: TestSatWidenMulPairwiseAdd in the Google Highway Test " john_platts at hotmail dot com
2023-08-09 13:16 ` [Bug target/110960] " john_platts at hotmail dot com
2023-08-09 13:19 ` [Bug target/110960] TestSatWidenMulPairwiseAdd in the Google Highway test " john_platts at hotmail dot com
2023-08-09 13:22 ` john_platts at hotmail dot com
2023-08-09 16:10 ` john_platts at hotmail dot com
2023-08-09 16:11 ` john_platts at hotmail dot com
2023-08-10 13:50 ` john_platts at hotmail dot com
2023-09-08 9:19 ` malat at debian dot org
2023-09-08 15:58 ` pinskia at gcc dot gnu.org [this message]
2023-09-09 17:47 ` john_platts at hotmail dot com
2023-09-09 17:59 ` john_platts at hotmail dot com
2023-09-09 20:05 ` john_platts at hotmail dot com
2024-03-29 18:11 ` meissner 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-110960-4-96SEBHKhZG@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).