On Tue, Mar 13, 2018 at 07:00:17PM +0100, Luc Van Oostenryck wrote: > The issue here is that sparse has a whole class of warnings that are > given very early (here at expansion of constant expressions), before > eliminating code from branches that are never taken (which, surprise, > need itself to have constant expressions already expanded). > > It's often annoying like the case here. > OTOH, I don't think it's always a bad thing. Sometimes we want to > have warnings even from code we know will not be executed (in this > config but maybe it will in another one). Is that really a valid concern with all the automated randconfig building going on today? -- 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
