[cfe-dev] clang plugin

[Daniel Dunbar]

On Sat, Apr 3, 2010 at 5:54 AM, Christof Meerwald <cmeerw at cmeerw.org> wrote:
> On Fri, 2 Apr 2010 11:05:40 +0900, Naoya Maruyama wrote:
>> I'm developing a c-program tool with clang, and trying the
>> PrintFunctionNames plugin. However, running a command loading plugin
>> libraries doesn't seem to find plugins:
>>
>>  $ clang -cc1 -load path/to/libPrintFunctionNames.so -plugin help
>> clang -cc1 plugins:
>
> I have come across the same problem recently. I think it's caused by the
> plugin shared library using its own instance of the plugin registry instead
> of the one from the clang binary. The way I fixed (or worked around) it on
> my system was by changing autoconf/ExportMap.map (and rebuilding clang) as
> follows:
>
> {
>        global: main;
>                __progname;
>                environ;
>                _ZN4llvm8RegistryIN5clang14FrontendActionENS_14RegistryTraitsIS2_EEE4HeadE;
>
>        local: *;
> };
>

Yes, unfortunately the plugin mechanism is currently limited &
confusing because of how we handle symbol exports. I'm tempted to just
remove the current example and recommend people follow the
clang-interpreter example instead, until someone takes the plugin
mechanism and really makes it robust & usable. Any objections?

 - Daniel

> Christof
>
> --
>
> http://cmeerw.org                              sip:cmeerw at cmeerw.org
> mailto:cmeerw at cmeerw.org                   xmpp:cmeerw at cmeerw.org
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>