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/102658] [12 regression] Many test case failures after r12-4240
Date: Wed, 13 Oct 2021 05:22:26 +0000 [thread overview]
Message-ID: <bug-102658-4-zZAy1ZxZJf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102658-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102658
--- Comment #8 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:a124c1b0a2595f285c0d8ed863b37b83e14a6566
commit r12-4364-ga124c1b0a2595f285c0d8ed863b37b83e14a6566
Author: Kewen Lin <linkw@linux.ibm.com>
Date: Wed Oct 13 00:20:45 2021 -0500
rs6000/test: Adjust test cases due to O2 vect [PR102658]
Commit r12-4240 enables vectorization at O2, this patch is to
adjust some test cases for rs6000 port accordingly.
It simply adds -fno-tree-vectorize to retain original test points.
gcc/testsuite/ChangeLog:
PR testsuite/102658
* gcc.target/powerpc/dform-1.c: Adjust as vectorization enabled at
O2.
* gcc.target/powerpc/dform-2.c: Likewise.
* gcc.target/powerpc/pr80510-2.c: Likewise.
next prev parent reply other threads:[~2021-10-13 5:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 21:52 [Bug testsuite/102658] New: " seurer at gcc dot gnu.org
2021-10-09 1:06 ` [Bug testsuite/102658] " crazylht at gmail dot com
2021-10-09 1:51 ` linkw at gcc dot gnu.org
2021-10-09 2:04 ` linkw at gcc dot gnu.org
2021-10-09 10:39 ` linkw at gcc dot gnu.org
2021-10-11 8:37 ` rguenth at gcc dot gnu.org
2021-10-11 14:54 ` msebor at gcc dot gnu.org
2021-10-13 2:18 ` linkw at gcc dot gnu.org
2021-10-13 2:24 ` linkw at gcc dot gnu.org
2021-10-13 5:22 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-13 5:49 ` linkw at gcc dot gnu.org
2021-10-13 5:51 ` crazylht at gmail dot com
2021-10-13 5:57 ` linkw at gcc dot gnu.org
2021-10-20 6:30 ` linkw 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-102658-4-zZAy1ZxZJf@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).