Hi, I would like to assert that in the C code there was no attempt to access uninitialized value. If you have a look at the original report here: http://marc.info/?l=linux-sparse&m=149070715427276&w=2 You will see that the C code assigns a value to the field before attempting to access it as shown below. s3.onebit = 1; if(s3.onebit != 1){ } It might be useful to step back and explore how should code be generated for this such that it is not treated as uninitialized value. Regards Dibyendu -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
