Re: Plugin: global vs global static in c/c++ AST representation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 27.05.2013 10:10, schrieb Florian Weimer:

> <https://github.com/fweimer/symboldb/blob/master/doc/examples/library-symbol-collisions.txt>
> 
> 
> I think you can cut down the number of false positives by taking ELF
> binding types into account (which I have not investigated yet).
> 
I allready tried objdump and nm and size but there are some difficulty.
I found it very hard to separate "static within function", "global" and
"global static".
It does not easyly provide the location in the source file.
It does not allow me to insult the develloper at compile time.
Even if i could fix it by now it just takes just a few months and the
clash may happen again.
I think i'd go for the plugin solution and reinvestiagte the c-frontend.
In c++ i'm very positive about the decl_this_staic predicate.




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux