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/111489] [12/13 Regression] Incorrect "-Wmaybe-uninitialized" warning from GCC 13.2.0
Date: Fri, 10 Nov 2023 14:24:13 +0000 [thread overview]
Message-ID: <bug-111489-4-WRqqO4HM4c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111489-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111489
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:06ee3438a4fcf98031fccda8ea8ff592a41cf218
commit r13-8039-g06ee3438a4fcf98031fccda8ea8ff592a41cf218
Author: Richard Biener <rguenther@suse.de>
Date: Wed Sep 20 08:40:34 2023 +0200
tree-optimization/111489 - turn uninit limits to params
The following turns MAX_NUM_CHAINS and MAX_CHAIN_LEN to params which
allows to experiment with raising them. For the testcase in PR111489
raising MAX_CHAIN_LEN from 5 to 8 avoids the bogus diagnostics
at -O2, at -O3 we need a MAX_CHAIN_LEN of 6.
PR tree-optimization/111489
* doc/invoke.texi (--param uninit-max-chain-len): Document.
(--param uninit-max-num-chains): Likewise.
* params.opt (-param=uninit-max-chain-len=): New.
(-param=uninit-max-num-chains=): Likewise.
* gimple-predicate-analysis.cc (MAX_NUM_CHAINS): Define to
param_uninit_max_num_chains.
(MAX_CHAIN_LEN): Define to param_uninit_max_chain_len.
(uninit_analysis::init_use_preds): Avoid VLA.
(uninit_analysis::init_from_phi_def): Likewise.
(compute_control_dep_chain): Avoid using MAX_CHAIN_LEN in
template parameter.
(cherry picked from commit b8a2a12464d25c45a51c14a025e8e2d3ca8ebeb0)
next prev parent reply other threads:[~2023-11-10 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 22:48 [Bug c/111489] New: " jonathan.leffler at gmail dot com
2023-09-19 23:15 ` [Bug tree-optimization/111489] " pinskia at gcc dot gnu.org
2023-09-19 23:15 ` pinskia at gcc dot gnu.org
2023-09-20 6:34 ` rguenth at gcc dot gnu.org
2023-09-20 6:47 ` rguenth at gcc dot gnu.org
2023-09-20 9:20 ` cvs-commit at gcc dot gnu.org
2023-09-20 9:22 ` [Bug tree-optimization/111489] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org
2024-06-20 9:14 ` [Bug tree-optimization/111489] [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-111489-4-WRqqO4HM4c@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).