On Thu, Jun 26, 2014 at 11:02:18AM +0200, Alexander Aring wrote:
Hi Sascha,
I get this warning about 1 month and it makes me crazy and I am unsing
gcc (GCC) 4.9.0 20140604 (prerelease).
Why I didn't sent any patches?
Because you say it here it's a compiler bug and the linux world
gcc-4.9 is too silly to recognize that *jump cannot be used
uninitialized and issues a warning. Explicitly initialize
*jump to avoid the warning.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
scripts/kconfig/menu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Sascha,
I get this warning about 1 month and it makes me crazy and I am unsing
gcc (GCC) 4.9.0 20140604 (prerelease).
Why I didn't sent any patches?
Because you say it here it's a compiler bug and the linux world doesn't
fix it this way. Look at [0].
... since we will still want to catch
