public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	mmarek@suse.cz, akpm@linux-foundation.org
Subject: Re: [PATCH] scripts/kconfig/menu.c: warning: jump may be used uninitialized in this function
Date: Wed, 30 Oct 2013 11:03:23 +0530	[thread overview]
Message-ID: <52709A23.9060204@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131029175354.GB3411@free.fr>

On Tuesday 29 October 2013 11:23 PM, Yann E. MORIN wrote:
> Christian, All,
> 
> On 2013-10-27 19:02 -0700, Christian Kujau spake thusly:
>> On Sun, 27 Oct 2013 at 18:28, Christian Kujau wrote:
>>> While doing "make oldconfig" on 3.12-rc7 with gcc-4.7.2 (Debian), the 
>>> following warning is printed:
>>>
>>>   HOSTCC  scripts/kconfig/zconf.tab.o
>>> In file included from scripts/kconfig/zconf.tab.c:2537:0:
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c: In function ‘get_symbol_str’:
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c:586:18: warning: ‘jump’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c:547:19: note: ‘jump’ was declared here
>>
>> Grrr, only after I sent this message I found this was reported in 
>> September already by Madhavan Srinivasan:  https://lkml.org/lkml/2013/9/19/24
>>
>> Does anybody know the state of this fix?
> 
My bad, somehow this slipped from my todo list.

> The solution was to properly comment that this was a gcc issue, in that 
> this is a spurious error, does not appear in previous gcc versions, and
> has been fixed in later gcc versions.
> 
I also notice this with gcc 4.8.1 (20131002) build.

> Setting 'jump' to NULL may hide reall issues in case the code is changed
> in the future, so it is not appropriate a fix. Hence why the previously-
> submitted patches were not applied.
> 
> I'll take this on me to properly fix this. Thanks for the heads up.
> 
> Regards,
> Yann E. MORIN.
> 


      reply	other threads:[~2013-10-30  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28  1:28 [PATCH] scripts/kconfig/menu.c: warning: jump may be used uninitialized in this function Christian Kujau
2013-10-28  2:02 ` Christian Kujau
2013-10-29 17:53   ` Yann E. MORIN
2013-10-30  5:33     ` Madhavan Srinivasan [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=52709A23.9060204@linux.vnet.ibm.com \
    --to=maddy@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=mmarek@suse.cz \
    --cc=yann.morin.1998@free.fr \
    /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