On Thu, Jan 4, 2018 at 12:41 AM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: >> >> yeah, it seems odd (and annoying at the same time) that ctags emits internal symbols __builtin_bswap16 and similar stuff, unlike exuberant ctags. > > There is several ways to change this but I need to think a bit > about it. The builtin needs to be in the global scope because we don't want to lose those function when sparse switch to the next C files. > > There is also that sparse's ctags work on the preprocessed source > while, I think, other ctags work purely on the lexical level, > thus on non-preprocessed sources. Yes, that is by design. It is a useful feature to find out those symbol generated from the macro expansion. I have one idea, I haven't look closely how piratical it is. I think we can filter out the __buildin_xxx functions by looking at the some builtin flags in the symbol. Chris -- 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
