[LLVMdev] getting gold plugin to work?

[Sandeep Patel]

On Mon, Oct 5, 2009 at 8:04 PM, Rafael Espindola <espindola at google.com> wrote:
>> I have no idea how to reduce this.
>>
>> Configure llvm-gcc for "arm-eabi" and use "--with-cpu=cortex-a8
>> --with-fpu=neon --with-abi=aapcs --with-float=hard". The triple in the
>> bitcode will be "armv7-eabi" but the actual CPU subtarget won't be
>> known to the gold plugin. I'd think the same would be true for any
>> cross-compiler. Note that self-hosting X86 will eventually use a CPUID
>> instruction to determine the proper subtarget on the fly so it will
>> usually be correct.
>
> I will try to take a look, but it will take some time.

If we can decide the way we want the options passed, I can take a stab
at it (or more likely Viktor will).

I'd expect that gold will need an option that tells it that some
following option or options are to be passed to the plugin. The plugin
API will need to pass these flags down. Any suggestions here that
would be compatible with the FSF view of the universe would be
welcome.

I assume the plugin's options should be either the existing cl::opt
ones (-mcpu, etc.) or similar to the llc ones.

deep