LTO and LTO Plugin Reviewers
Basile STARYNKEVITCH
basile@starynkevitch.net
Wed Oct 7 14:29:00 GMT 2009
Diego Novillo wrote:
> On Wed, Oct 7, 2009 at 10:10, Basile STARYNKEVITCH
> <basile@starynkevitch.net> wrote:
>
>> Then I would imagine it requires a copyright transfer to FSF different of
>> the one covering GCC development. The legal document covering my
>> contribution cites specifically GCC (not binutils).
>>
>> Getting that copyright transfer signed by my employer was so painful that I
>> would never go thru that again :-( :-(
>>
>> But then, I would imagine that LTO plugins only discussion should go to a
>> binutils or a gold list [which I don't subscribe to], not a gcc one!
>
> What are you talking about?
on a recent gcc trunk rev 152527
grep -rn dlopen | fgrep .c:
gives
gcc/plugin.c:418: dl_handle = dlopen (plugin->full_name, RTLD_NOW
RTLD_GLOBAL);
lto-plugin/lto-symtab.c:140: plugin_handle = dlopen (name, RTLD_LAZY);
and other occurrences java or mudflap related
I suppose LTO plugins means plugin dlopen-ed in lto-plugin/lto-symtab.c
Are these inside the cc1 process? is GGC (that is gengtype GTY-ed
garbage collection) usable from them?
[my blind guess is no to both questions!]
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
More information about the Gcc
mailing list