From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Cc: mmarek@suse.cz, bpoirier@suse.de, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] kconfig/menu.c: fix uninitialized variable warning
Date: Thu, 26 Sep 2013 19:05:20 +0200 [thread overview]
Message-ID: <20130926170520.GB3418@free.fr> (raw)
In-Reply-To: <1379869557-23116-1-git-send-email-maddy@linux.vnet.ibm.com>
Madhavan, All,
On 2013-09-22 22:35 +0530, Madhavan Srinivasan spake thusly:
> In file included from scripts/kconfig/zconf.tab.c:2537:0:
> scripts/kconfig/menu.c: In function ‘get_symbol_str’:
> scripts/kconfig/menu.c:586:18: warning: ‘jump’ may be used uninitialized in
> this function [-Wmaybe-uninitialized]
> jump->offset = r->len - 1;
> ^
> scripts/kconfig/menu.c:547:19: note: ‘jump’ was declared here
> struct jump_key *jump;
> ^
> Change V2:
>
> 1)Added comment as suggested.
Maybe I'm mislead, but I think Benjamin and I suggested a comment that
explained the warning was just spurious, and there would be no code
change. Something like:
/* gcc 4.8.0 on (your distro and version) warns about 'jump may be
* used uninitialized', which is wrong. The warning does not appear
* with gcc != 4.8.0 */
struct jump_key *jump;
This is so, if sometime in the future the code changes, and the variable
is indeeded used uninitialised, we have a proper warning by gcc in this
case.
Care to resend, please?
Regards,
Yann E. MORIN.
> Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
> ---
> scripts/kconfig/menu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
> index c1d5320..32ee2d5 100644
> --- a/scripts/kconfig/menu.c
> +++ b/scripts/kconfig/menu.c
> @@ -544,7 +544,8 @@ static void get_prompt_str(struct gstr *r, struct property *prop,
> {
> int i, j;
> struct menu *submenu[8], *menu, *location = NULL;
> - struct jump_key *jump;
> + /* Initializing to avoid a spurious warning observed in gcc 4.8.0 */
> + struct jump_key *jump = NULL;
>
> str_printf(r, _("Prompt: %s\n"), _(prop->text));
> menu = prop->menu->parent;
> --
> 1.7.10.4
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2013-09-26 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 17:05 =?y?q?=5BPATCH=20V2=5D=20kconfig/menu=2Ec=3A=20fix=20uninitialized=20variable=20warning?= Madhavan Srinivasan
2013-09-26 17:05 ` Yann E. MORIN [this message]
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=20130926170520.GB3418@free.fr \
--to=yann.morin.1998@free.fr \
--cc=bpoirier@suse.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mmarek@suse.cz \
/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