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 middle-end/106196] [13 Regression] vect_do_peeling ICE since g:3769ad4ccea9589b3f7edaef901cb542aa10f49a
Date: Tue, 05 Jul 2022 10:56:00 +0000 [thread overview]
Message-ID: <bug-106196-4-qbvQjzdfnc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106196-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106196
--- Comment #2 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:1a6e0d8252a71c61d4dc616044fb25b5ac2cfffb
commit r13-1502-g1a6e0d8252a71c61d4dc616044fb25b5ac2cfffb
Author: Richard Biener <rguenther@suse.de>
Date: Tue Jul 5 10:43:42 2022 +0200
tree-optimization/106196 - properly update virtual SSA for vector stores
The following properly handles aggregate returns of the const marked
STORE_LANES internal function to update virtual SSA form on-the-fly
rather than relying on a costly virtual SSA rewrite.
PR tree-optimization/106196
* tree-vect-stmts.cc (vect_finish_stmt_generation): Properly
handle aggregate returns of calls for VDEF updates.
* gcc.dg/torture/pr106196.c: New testcase.
next prev parent reply other threads:[~2022-07-05 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 6:14 [Bug middle-end/106196] New: " tnfchris at gcc dot gnu.org
2022-07-05 8:34 ` [Bug middle-end/106196] " rguenth at gcc dot gnu.org
2022-07-05 10:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-05 10:56 ` rguenth at gcc dot gnu.org
2022-07-08 11:35 ` tnfchris at gcc dot gnu.org
2022-07-08 11:53 ` rguenth at gcc dot gnu.org
2022-07-08 11:58 ` tnfchris at gcc dot gnu.org
2022-07-08 12:51 ` 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-106196-4-qbvQjzdfnc@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).