On Thu, Aug 31, 2017 at 6:34 AM, Josh Poimboeuf <jpoimboe@xxxxxxxxxx> wrote:
>
> I think I'm seeing a bug in the sparse preprocessor. I've reduced it to
> the following test case.
I think the real reduced test-case is just this:
#define ARGS_APPEND(...) ,## __VA_ARGS__
ARGS_APPEND()
and you can run if through "sparse -E" to see the comma (while gcc -E
does not have it).
I'm adding Al to the cc list because he's the pre-processor person.
Hopefully he has gotten out from under most of his emails from his
move.
sparse gets it right if there is any non-VA_ARGS argument to the
symbol, but not if __VA_ARGS__ is all of the argument to the macro.
Al?
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
