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/108816] ICE in operator[], at vec.h:889
Date: Mon, 20 Feb 2023 10:56:05 +0000 [thread overview]
Message-ID: <bug-108816-4-hpaBAzXlQl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108816-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108816
--- 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:63471c5008819bbf6ec32a6f4d8701fe57b96fa9
commit r13-6140-g63471c5008819bbf6ec32a6f4d8701fe57b96fa9
Author: Richard Biener <rguenther@suse.de>
Date: Mon Feb 20 10:59:15 2023 +0100
tree-optimization/108816 - vect versioning check split confusion
The split of the versioning condition assumes the definition is
in the condition block which is ensured by the versioning code.
But that only works when we actually have to insert any statements
for the versioning condition. The following adjusts the guard
accordingly and asserts this condition.
PR tree-optimization/108816
* tree-vect-loop-manip.cc (vect_loop_versioning): Adjust
versioning condition split prerequesite, assert required
invariant.
* gcc.dg/torture/pr108816.c: New testcase.
next prev parent reply other threads:[~2023-02-20 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 2:44 [Bug target/108816] New: " asolokha at gmx dot com
2023-02-17 7:58 ` [Bug tree-optimization/108816] " rguenth at gcc dot gnu.org
2023-02-20 9:59 ` rguenth at gcc dot gnu.org
2023-02-20 10:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-20 10:57 ` [Bug tree-optimization/108816] [12 Regression] " rguenth at gcc dot gnu.org
2023-03-15 9:48 ` cvs-commit at gcc dot gnu.org
2023-03-15 10:04 ` 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-108816-4-hpaBAzXlQl@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).