public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61677] False positive with -Wmaybe-uninitialized (predicate analysis, VRP)
Date: Mon, 29 Mar 2021 21:29:25 +0000 [thread overview]
Message-ID: <bug-61677-4-NxB00lJ2ku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61677-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61677
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
The false positive for the reduced test case from comment #4 was fixed by
r220696. r11-7898 adds it to the testsuite. The unreduced test case from
attachment 33055 still warns with GCC 11:
$ gcc -O2 -S -Wall pr61677-c0.c
In file included from scripts/kconfig/zconf.tab.c:2537:
scripts/kconfig/menu.c: In function ‘get_symbol_str’:
scripts/kconfig/menu.c:590:18: warning: ‘jump’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
In file included from scripts/kconfig/zconf.tab.c:2537:
scripts/kconfig/menu.c:551:19: note: ‘jump’ was declared here
next prev parent reply other threads:[~2021-03-29 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 22:24 [Bug c/61677] New: False positive with -Wmaybe-uninitialized (test case included) josh at joshtriplett dot org
2014-07-03 6:51 ` [Bug middle-end/61677] " schwab@linux-m68k.org
2014-07-03 15:17 ` manu at gcc dot gnu.org
2014-07-03 15:26 ` manu at gcc dot gnu.org
2021-03-29 21:23 ` [Bug middle-end/61677] False positive with -Wmaybe-uninitialized (predicate analysis, VRP) cvs-commit at gcc dot gnu.org
2021-03-29 21:29 ` msebor at gcc dot gnu.org [this message]
2022-08-29 14:26 ` [Bug tree-optimization/61677] " 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-61677-4-NxB00lJ2ku@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).