Displaying 6 results from an estimated 6 matches for "cofff".
Did you mean:
coff
2017 Feb 14
2
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
>
> No, I meant an even thinner wrapper which textually translates arguments.
> For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o
> foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything
> with Config object nor LinkerDriver::run and have absolutely zero knowledge
> on the internals of LLD.
Ohh okay I misunderstood.
(Why I'm asking this is because I want to sure that there's no difference
> between the regular Windows linker and...
2017 Feb 14
2
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
...ell Malone <martellmalone at gmail.com>
> wrote:
>
>> No, I meant an even thinner wrapper which textually translates arguments.
>>> For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o
>>> foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything
>>> with Config object nor LinkerDriver::run and have absolutely zero knowledge
>>> on the internals of LLD.
>>
>> Ohh okay I misunderstood.
>>
>> (Why I'm asking this is because I want to sure that there's no diff...
2017 Feb 14
2
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
...017 at 4:46 PM, Martell Malone <martellmalone at gmail.com>
> wrote:
>
> No, I meant an even thinner wrapper which textually translates arguments.
> For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o
> foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything
> with Config object nor LinkerDriver::run and have absolutely zero knowledge
> on the internals of LLD.
>
> Ohh okay I misunderstood.
>
> (Why I'm asking this is because I want to sure that there's no difference
> between the regular...
2017 Feb 14
2
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
...017 at 4:46 PM, Martell Malone <martellmalone at gmail.com>
> wrote:
>
> No, I meant an even thinner wrapper which textually translates arguments.
> For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o
> foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything
> with Config object nor LinkerDriver::run and have absolutely zero knowledge
> on the internals of LLD.
>
> Ohh okay I misunderstood.
>
> (Why I'm asking this is because I want to sure that there's no difference
> between the regular...
2017 Feb 14
3
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
...017 at 4:46 PM, Martell Malone <martellmalone at gmail.com>
> wrote:
>
> No, I meant an even thinner wrapper which textually translates arguments.
> For example, the wrapper would translates "/out:foo.exe foo.obj" to "-o
> foo.exe foo.obj" and then call lld::COFFF:link(). It doesn't do anything
> with Config object nor LinkerDriver::run and have absolutely zero knowledge
> on the internals of LLD.
>
> Ohh okay I misunderstood.
>
> (Why I'm asking this is because I want to sure that there's no difference
> between the regular...
2017 Feb 13
2
RFC: A new llvm-dlltool driver and llvm-lib driver improvements
>
> I wonder if it can be a wrapper for LLD/COFF. It can be an in-process
> wrapper, meaning that you could add a main function for mingw which
> translates all arguments into the MSVC style and then invoke the COFF
> linker's main function.
That should work, if I am understanding this correctly I can create an
argument parser (probably partially based on the ELF one) then I