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/96109] [11/12 Regression] gcc.dg/vect/slp-47.c etc. FAIL
Date: Tue, 26 Oct 2021 10:30:06 +0000 [thread overview]
Message-ID: <bug-96109-4-FrkdN4M9V6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96109-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96109
--- Comment #9 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:94f28340513753ba94ab483e93ce1d096842a5ad
commit r12-4706-g94f28340513753ba94ab483e93ce1d096842a5ad
Author: Richard Biener <rguenther@suse.de>
Date: Mon Oct 25 13:39:07 2021 +0200
Move negative stride bias out of dr_misalignment
This moves applying of a bias for negative stride accesses out of
dr_misalignment in favor of a more general optional offset argument.
The negative bias is now computed by get_load_store_type and applied
accordingly to determine the alignment support scheme. Likewise
the peeling/versioning code is adjusted albeit that still assumes
we'll end up with VMAT_CONTIGUOUS_DOWN or VMAT_CONTIGUOUS_REVERSE
but at least when not so (VMAT_STRIDED_SLP is one possibility) then
get_load_store_type will _not_ falsely report an aligned access but
instead an access with known misalignment.
This fixes PR96109.
2021-10-25 Richard Biener <rguenther@suse.de>
PR tree-optimization/96109
* tree-vectorizer.h (dr_misalignment): Add optional offset
parameter.
* tree-vect-data-refs.c (dr_misalignment): Likewise. Remove
offset applied for negative stride accesses.
(vect_enhance_data_refs_alignment): Compute negative stride
access offset and pass it to dr_misalignment.
* tree-vect-stmts.c (get_negative_load_store_type): Pass
negative offset to dr_misalignment.
(get_group_load_store_type): Likewise.
(get_load_store_type): Likewise.
(vectorizable_store): Remove asserts about alignment.
(vectorizable_load): Likewise.
next prev parent reply other threads:[~2021-10-26 10:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 8:51 [Bug testsuite/96109] New: " ro at gcc dot gnu.org
2020-07-08 8:53 ` [Bug testsuite/96109] " ro at gcc dot gnu.org
2020-07-08 8:53 ` ro at gcc dot gnu.org
2020-07-08 9:18 ` rguenth at gcc dot gnu.org
2020-07-08 9:41 ` rguenth at gcc dot gnu.org
2020-07-10 12:26 ` clyon at gcc dot gnu.org
2021-01-19 9:11 ` [Bug testsuite/96109] [11 Regression] " rguenth at gcc dot gnu.org
2021-01-19 9:23 ` rguenth at gcc dot gnu.org
2021-04-27 11:39 ` [Bug testsuite/96109] [11/12 " jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2021-10-26 10:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-26 10:30 ` [Bug testsuite/96109] [11 " rguenth at gcc dot gnu.org
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2023-05-29 10:03 ` jakub at gcc dot gnu.org
2023-08-25 18:09 ` dcb314 at hotmail dot com
2023-08-25 18:10 ` dcb314 at hotmail dot com
2024-02-23 9:36 ` ro at gcc dot gnu.org
2024-02-23 9:37 ` ro at gcc dot gnu.org
2024-03-11 14:45 ` cvs-commit at gcc dot gnu.org
2024-03-11 14:54 ` 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-96109-4-FrkdN4M9V6@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).