public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102949] [12 regression] gcc.dg/vect/slp-reduc-1.c FAIL
Date: Wed, 27 Oct 2021 06:52:54 +0000 [thread overview]
Message-ID: <bug-102949-4-okoYp2haXn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102949-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102949
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-10-27
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Keywords| |wrong-code
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Surely mine, in the range of revs the relevant one would be
commit 4703182a06b831a9f47a5f8198e86042cadd938d
Author: Richard Biener <rguenther@suse.de>
Date: Fri Sep 17 12:48:09 2021 +0200
Revert no longer needed fix for PR95539
The workaround is no longer necessary since we maintain alignment
info on the DR group leader only.
2021-09-17 Richard Biener <rguenther@suse.de>
* tree-vect-stmts.c (vectorizable_load): Do not frob
stmt_info for SLP.
next prev parent reply other threads:[~2021-10-27 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:54 [Bug tree-optimization/102949] New: " ro at gcc dot gnu.org
2021-10-26 14:54 ` [Bug tree-optimization/102949] " ro at gcc dot gnu.org
2021-10-27 6:52 ` rguenth at gcc dot gnu.org [this message]
2021-10-28 8:10 ` rguenth at gcc dot gnu.org
2021-10-28 8:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-10-28 8:23 ` ebotcazou at gcc dot gnu.org
2021-10-28 8:25 ` rguenth at gcc dot gnu.org
2021-10-28 9:02 ` cvs-commit at gcc dot gnu.org
2021-10-28 9:03 ` rguenth at gcc dot gnu.org
2021-10-29 7:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-102949-4-okoYp2haXn@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).