public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63748] New: may be used uninitialized warning on variable definition with initializer
Date: Wed, 05 Nov 2014 12:52:00 -0000 [thread overview]
Message-ID: <bug-63748-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63748
Bug ID: 63748
Summary: may be used uninitialized warning on variable
definition with initializer
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: amodra at gmail dot com
Created attachment 33892
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33892&action=edit
preprocessed source
Found when compiling gdb's eval.c using gcc-4.9.1 or current trunk,
x86_64-linux or powerpc64-linux.
/src/binutils-gdb/gdb/eval.c: In function ‘evaluate_subexp_standard’:
/src/binutils-gdb/gdb/eval.c:745:16: error: ‘ret’ may be used uninitialized in
this function [-Werror=maybe-uninitialized]
struct value *ret = NULL;
^
More bogus warnings follow with -O -Wall on the attached preprocessed source.
>From gcc-bugs-return-465795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 05 12:55:02 2014
Return-Path: <gcc-bugs-return-465795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30346 invoked by alias); 5 Nov 2014 12:55:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29994 invoked by uid 48); 5 Nov 2014 12:54:58 -0000
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/61033] [4.8/4.9 Regression] Infinite loop in variable tracking
Date: Wed, 05 Nov 2014 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mkuvyrkov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: michael.collison at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61033-4-ZgAkZNBGvR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg00267.txt.bz2
Content-length: 175
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida033
--- Comment #10 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> ---
Michael,
What is the status of this bug?
Thanks.
next reply other threads:[~2014-11-05 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 12:52 amodra at gmail dot com [this message]
2014-11-05 13:15 ` [Bug tree-optimization/63748] [4.9/5 Regression] " mpolacek at gcc dot gnu.org
2014-11-07 21:57 ` uweigand at gcc dot gnu.org
2014-11-07 22:42 ` uweigand at gcc dot gnu.org
2014-11-10 12:48 ` [Bug tree-optimization/63748] [4.9/5 Regression] wrong may be used uninitialized warning (abnormal edges) uweigand at gcc dot gnu.org
2014-11-10 20:44 ` ppalka at gcc dot gnu.org
2014-11-11 5:23 ` amodra at gmail dot com
2014-11-24 13:49 ` [Bug tree-optimization/63748] [4.9 " rguenth at gcc dot gnu.org
2014-11-24 16:56 ` rguenth at gcc dot gnu.org
2015-02-23 18:30 ` manu at gcc dot gnu.org
2015-06-26 20:18 ` jakub at gcc dot gnu.org
2015-06-26 20:38 ` jakub 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-63748-4@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).