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/67196] [10/11/12/13 Regression] loop-induced false positive from -Wmaybe-uninitialized
Date: Tue, 30 Aug 2022 11:15:31 +0000 [thread overview]
Message-ID: <bug-67196-4-EqYFHsAyWl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67196-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67196
--- Comment #8 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:61051ee5cfd59ee292984641d02caac85f6dfac3
commit r13-2273-g61051ee5cfd59ee292984641d02caac85f6dfac3
Author: Richard Biener <rguenther@suse.de>
Date: Tue Aug 30 11:47:49 2022 +0200
tree-optimization/67196 - normalize use predicates earlier
The following makes sure to have use predicates simplified and
normalized before doing uninit_analysis::overlap because that
otherwise cannot pick up all flag setting cases. This fixes
half of the issue in PR67196 and conveniently resolves the
XFAIL in gcc.dg/uninit-pred-7_a.c.
PR tree-optimization/67196
* gimple-predicate-analysis.cc (uninit_analysis::is_use_guarded):
Simplify and normalize use prediates before first use.
* gcc.dg/uninit-pred-7_a.c: Un-XFAIL.
next prev parent reply other threads:[~2022-08-30 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 19:03 [Bug tree-optimization/67196] New: Another " dmalcolm at gcc dot gnu.org
2015-08-12 20:26 ` [Bug tree-optimization/67196] " manu at gcc dot gnu.org
2021-03-31 19:44 ` [Bug tree-optimization/67196] [9/10/11 Regression] loop-induced " msebor at gcc dot gnu.org
2021-04-08 14:24 ` rguenth at gcc dot gnu.org
2021-06-01 8:06 ` [Bug tree-optimization/67196] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-01-21 13:53 ` rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug tree-optimization/67196] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2022-08-30 9:40 ` rguenth at gcc dot gnu.org
2022-08-30 11:15 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-20 3:56 ` [Bug tree-optimization/67196] [10/11/12 " law at gcc dot gnu.org
2022-11-21 6:47 ` rguenth at gcc dot gnu.org
2023-07-07 7:28 ` [Bug tree-optimization/67196] [11/12 " 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-67196-4-EqYFHsAyWl@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).