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/102905] [12 regression] several vector test cases fail on power 7 after r12-4490
Date: Mon, 25 Oct 2021 10:49:37 +0000 [thread overview]
Message-ID: <bug-102905-4-bC9mWD7th7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102905-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102905
--- Comment #3 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:0b028fb4989c2bdfaf474b4493c5926fb40da3c3
commit r12-4660-g0b028fb4989c2bdfaf474b4493c5926fb40da3c3
Author: Richard Biener <rguenther@suse.de>
Date: Mon Oct 25 11:33:10 2021 +0200
tree-optimization/102905 - restore re-align load for alignment peeling
Previous refactoring made the possibility of considering re-aligned
loads for unlimited cost model alignment peeling difficult so I
ditched that. Later refactoring made it easily possible again so
the following patch re-instantiates this which should fix the
observed regression on powerpc with altivec.
2021-10-25 Richard Biener <rguenther@suse.de>
PR tree-optimization/102905
* tree-vect-data-refs.c (vect_enhance_data_refs_alignment):
Use vect_supportable_dr_alignment again to determine whether
an access is supported when not aligned.
next prev parent reply other threads:[~2021-10-25 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 18:56 [Bug testsuite/102905] New: " seurer at gcc dot gnu.org
2021-10-22 21:20 ` [Bug testsuite/102905] " pinskia at gcc dot gnu.org
2021-10-25 6:40 ` [Bug tree-optimization/102905] " rguenth at gcc dot gnu.org
2021-10-25 9:33 ` rguenth at gcc dot gnu.org
2021-10-25 10:49 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-25 10:49 ` 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-102905-4-bC9mWD7th7@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).