On 4/25/12 1:37 AM, Brett Foster wrote:
When I add:register_callback (BaseName, PLUGIN_FINISH_TYPE, CinsGcc_CB_Type, NULL); The plugin appears to be loaded by a 2nd process, initialized, and provided with what appears to be much the same data (at least from my view).
That's correct. All plugin events are emitted from cc1/cc1plus/f951/jc1/lto1. These binaries are the actual compiler. 'gcc' is a driver process that calls the compiler, the assembler, the linker, etc.
Other plugin events do not appear to cause this behaviour.
They should. All events are generated from the compiler, not the driver. Diego.
