From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized
Date: Tue, 25 Apr 2017 12:15:00 -0000 [thread overview]
Message-ID: <bug-21011-10460-xRaS7w4fIN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21011-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21011
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Mark Wielaard <mark at klomp dot org> ---
commit 7114c513fbebcca8b76796b7f64b57447ba383e1
Author: Mark Wielaard <mark@klomp.org>
Date: Wed Apr 19 17:07:46 2017 +0200
libelf: Initialize n to zero in elf_getarsym.
When building with gcc -Os it seems we can inline read_number_entries
but if that function fails then n will not be initialized. GCC seems not
to realize that in that case n won't be used at all. Explicitly initialize
n to zero to prevent a spurious error: 'n' may be used uninitialized in
this function [-Werror=maybe-uninitialized] in that case.
https://sourceware.org/bugzilla/show_bug.cgi?id=21011
Signed-off-by: Mark Wielaard <mark@klomp.org>
Pushed to master.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-04-24 9:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 21:38 [Bug general/21011] New: " luizluca at gmail dot com
2016-12-30 23:14 ` [Bug general/21011] " luizluca at gmail dot com
2016-12-30 23:20 ` pmachata at gmail dot com
2016-12-31 15:54 ` mjw at redhat dot com
2017-03-28 11:48 ` mark at klomp dot org
2017-04-04 5:37 ` luizluca at gmail dot com
2017-04-04 5:37 ` luizluca at gmail dot com
2017-04-04 5:38 ` luizluca at gmail dot com
2017-04-11 11:34 ` mark at klomp dot org
2017-04-17 19:51 ` luizluca at gmail dot com
2017-04-19 14:54 ` mark at klomp dot org
2017-04-19 15:14 ` mark at klomp dot org
2017-04-19 19:50 ` luizluca at gmail dot com
2017-04-19 19:58 ` mark at klomp dot org
2017-04-19 20:07 ` luizluca at gmail dot com
2017-04-25 3:38 ` mark at klomp dot org
2017-04-25 12:15 ` mark at klomp dot org [this message]
2017-04-25 12:49 ` luizluca at gmail dot com
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-21011-10460-xRaS7w4fIN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).