On 6 August 2017 at 19:15, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Sun, Aug 6, 2017 at 7:58 PM, Dibyendu Majumdar > <mobile@xxxxxxxxxxxxxxx> wrote: >> On 6 August 2017 at 18:45, Luc Van Oostenryck >> <luc.vanoostenryck@xxxxxxxxx> wrote: >>> On Sun, Aug 6, 2017 at 7:04 PM, Dibyendu Majumdar >>> <mobile@xxxxxxxxxxxxxxx> wrote: >>>> Wouldn't have thought so - as the variable is not initialized at the >>>> point of declaration. The assignment occurs after declaring the struct >>>> variable s3. >>> >>> IIRC, this patch was written specifically for the case you reported here. >>> >>>> I haven't tried that patch though. >>> >>> You'll need the full series: >>> https://github.com/lucvoo/sparse/tree/fix-bitfield-init-v3 >>> >> >> I will have a look at it. I did report separately the issue of not >> zeroing out structs when they are initialized and the change you >> mentioned earlier looks more for addressing that issue. > > Indeed. > I mixed up both (or more exactly, I thought it solved both). > The tests in your tree all are for initialization scenario - are you sure you fixed the issue mentioned in this thread? I will check later tonight and report back. 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
