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/102448] [12 Regression] wrong codegen in gcc in spec2017 since 24f99147b9264f8f7d9cfb2fa6bd431edfa252d2
Date: Thu, 23 Sep 2021 09:17:54 +0000 [thread overview]
Message-ID: <bug-102448-4-VIgGOSqK54@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102448-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102448
--- Comment #6 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:c0cc62b32d95caca25a8854e0d2b6f11f5674d30
commit r12-3839-gc0cc62b32d95caca25a8854e0d2b6f11f5674d30
Author: Richard Biener <rguenther@suse.de>
Date: Thu Sep 23 10:27:01 2021 +0200
tree-optimization/102448 - clear copied alignment info from vect
This fixes the previous change which removed setting alignment info
from the vectorizers idea of how a pointer is being used but left
in place the copied info from DR_PTR_INFO without realizing that this
is in fact _not_ the alignment of the access but the alignment of
a base pointer contained in it.
The following makes sure to not use that info.
2021-09-23 Richard Biener <rguenther@suse.de>
PR tree-optimization/102448
* tree-vect-data-refs.c (vect_duplicate_ssa_name_ptr_info):
Clear alignment info copied from DR_PTR_INFO.
next prev parent reply other threads:[~2021-09-23 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:07 [Bug tree-optimization/102448] New: " tnfchris at gcc dot gnu.org
2021-09-22 12:30 ` [Bug tree-optimization/102448] " rguenth at gcc dot gnu.org
2021-09-22 18:50 ` tnfchris at gcc dot gnu.org
2021-09-23 6:35 ` rguenth at gcc dot gnu.org
2021-09-23 6:54 ` rguenth at gcc dot gnu.org
2021-09-23 8:11 ` rguenth at gcc dot gnu.org
2021-09-23 9:17 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-23 9:18 ` rguenth at gcc dot gnu.org
2021-09-23 9:21 ` tnfchris 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-102448-4-VIgGOSqK54@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).