[LLVMdev] Updated RFC: ThinLTO Implementation Plan

[Dave Bozier]

> This sounds a little fragile and inflexible. How is the command line formed?

Our command line is processing is 100% compatible with GNU ld.

Sorry I think my earlier comment is confusing. I didn't mean order of
inputs placed on the command line. I meant the order of file types we
try to identify files as.

> At least for ELF, there is a e_machine field in the Elf header that can potentially be useful here.

Yes, this is what I was asking after.

>> Alternatively could we mark the native file header in a way that
>> identifies it as a bitcode wrapper is an option? That way we wouldn't
>> need to parse the section headers upfront to identify how the input
>> should be treated. This is possibly something we can look at as a
>> private change.