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/102861] [12 regression] gcc.dg/vect/bb-slp-16.c fails after r12-4526
Date: Thu, 21 Oct 2021 08:03:20 +0000 [thread overview]
Message-ID: <bug-102861-4-zlsfdutKFj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102861-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102861
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:d438dd2523a35e073eed04d146f1e73e2514d93d
commit r12-4593-gd438dd2523a35e073eed04d146f1e73e2514d93d
Author: Richard Biener <rguenther@suse.de>
Date: Thu Oct 21 10:00:27 2021 +0200
testsuite/102861 - adjust gcc.dg/vect/bb-slp-16.c change
This reverts the bogus previous change causing runtime failures
and instead realizes that we now have the loop condition
if-converted and the BB vectorization opportunity realized during
the loop vectorization pass.
2021-10-21 Richard Biener <rguenther@suse.de>
PR testsuite/102861
* gcc.dg/vect/bb-slp-16.c: Revert previous change, scan
the vect dump instead.
next prev parent reply other threads:[~2021-10-21 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:19 [Bug testsuite/102861] New: " seurer at gcc dot gnu.org
2021-10-20 18:22 ` [Bug testsuite/102861] " aldyh at gcc dot gnu.org
2021-10-20 19:41 ` pinskia at gcc dot gnu.org
2021-10-21 6:28 ` rguenth at gcc dot gnu.org
2021-10-21 7:12 ` aldyh at gcc dot gnu.org
2021-10-21 7:50 ` rguenther at suse dot de
2021-10-21 7:50 ` rguenth at gcc dot gnu.org
2021-10-21 7:53 ` aldyh at gcc dot gnu.org
2021-10-21 7:55 ` rguenth at gcc dot gnu.org
2021-10-21 8:03 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-21 8:03 ` rguenth 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-102861-4-zlsfdutKFj@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).