On Wed, Jan 03, 2018 at 03:57:43PM +0000, foobar wrote:
> On Tue, 2 Jan 2018 16:11:15 +0100
> Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote:
>
> > When creating builtin functions via init-builtins(), it shouldn't
> > really be needed to give them a type because their purpose is only
> > as a placeholder for the symbol->op->{evaluate,expand,..}. Also,
> > they should be part of the builtin_scope and never be visible.
>
> 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.
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.
Ciao and hanks for the bug repport
-- Luc
--
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
