On Sun, Mar 30, 2014 at 5:03 AM, Hans Verkuil <hverkuil@xxxxxxxxx> wrote:
>
> which is clearly a sparse bug somewhere.
Yes. What is going on is that we create separate symbols for each
declaration, and we tie them all together (and warn if they have
conflicting types).
But then when we look up a symbol, we only look at the latest one, so
when we size the array, we look at that "extern" declaration, and
don't see the size that was created with the initializer.
I'll think about how to fix it cleanly. Expect a patch shortly.
Linus
--
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
