So I went ahead and pushed your change, plus fixes for all the other warnings I got. Let me know if you find anything else.
Thanks! -- jzr P.S.: Fun fact! Your name crashed the server-side python scripts. That's probably why there's no mail about the commits. :D On 20 October 2017 at 01:49, Ondřej Hlavatý <[email protected]> wrote: > There are few of them, but this one is OK. The value is always > initialized, and apparantly GCC is able to prove it sometimes. > > Actually, most of the warnings I get with -Og are false alarms. Only > very few of them are real. That's why I think we should rather > explicitly turn on the magic yet unknown option, than to specify > unnecessary default values to silence GCC. Or a least make > maybe-uninitialized onlu a warning. > > What's even more strange, now I cannot reproduce it with -O3 neither. > But I'm pretty sure it was -O3. Also, I wasn't the first to notice this > behavior, Petr Mánek did (CCing him). Maybe he can add some details from > his side. > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
