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 doesn't > fix it this way. Look at [0]. > > "... since we will still want to catch unitialised use in the future, > should we were to changethe code." - which sounds useful. > > They already add a comment to this. I think otherwise they get much > patches because this warning. > > When I look into the current mainline code [1]. Then this is currently > not fixed in any way (comment or setting to NULL There is also the macro uninitialized_var (in both kernel and barebox) that could be used here instead of the explicit = NULL. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
