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 tree-optimization/96147] [11 regression] gcc.dg/vect/slp-43.c etc. FAIL
Date: Fri, 15 Jan 2021 13:05:29 +0000 [thread overview]
Message-ID: <bug-96147-4-AZCDKHUXxJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96147-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96147
--- 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:b36c9cd09472c8efb8405726b7cc94fa4ae7059f
commit r11-6715-gb36c9cd09472c8efb8405726b7cc94fa4ae7059f
Author: Richard Biener <rguenther@suse.de>
Date: Fri Jan 15 14:03:37 2021 +0100
testsuite/96147 - align vector access
This aligns p so that the testcase is meaningful for targets
without a hw misaligned access.
2021-01-15 Richard Biener <rguenther@suse.de>
PR testsuite/96147
* gcc.dg/vect/bb-slp-32.c: Align p.
next prev parent reply other threads:[~2021-01-15 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 8:23 [Bug tree-optimization/96147] New: " ro at gcc dot gnu.org
2020-07-10 8:25 ` [Bug tree-optimization/96147] " ro at gcc dot gnu.org
2020-07-10 8:25 ` ro at gcc dot gnu.org
2020-10-16 11:57 ` rguenth at gcc dot gnu.org
2020-12-08 11:54 ` rguenth at gcc dot gnu.org
2020-12-08 12:21 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-15 12:51 ` cvs-commit at gcc dot gnu.org
2021-01-15 12:53 ` cvs-commit at gcc dot gnu.org
2021-01-15 13:05 ` cvs-commit at gcc dot gnu.org
2021-01-15 13:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-15 13:06 ` rguenth at gcc dot gnu.org
2024-02-28 14:49 ` ro at gcc dot gnu.org
2024-02-28 14:49 ` ro at gcc dot gnu.org
2024-03-19 10:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-22 9:07 ` cvs-commit at gcc dot gnu.org
2024-03-22 9:12 ` ro 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-96147-4-AZCDKHUXxJ@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).