search for: thinlto_codegen_add_module

Displaying 7 results from an estimated 7 matches for "thinlto_codegen_add_module".

[ThinLTO] static library failure with object files with the same name
2017 Sep 17
2
[ThinLTO] static library failure with object files with the same name
...>>> >>>> Hi Johan, >>>> >>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>> in llvm/tools/lto/lto.cpp) >>>> >>>> For instance ThinLTOCodeGenerator::addModule is called >>>> through thinlto_codegen_add_module(). >>>> >>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>> if it is fixed in Xcode 9? >>>> (I think I remember fixing it in ld64 but I'm not totally sure...). >>>> >>> >>> I haven'...
[ThinLTO] static library failure with object files with the same name
2017 Sep 11
2
[ThinLTO] static library failure with object files with the same name
...17 at 5:44 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > >> Hi Johan, >> >> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >> in llvm/tools/lto/lto.cpp) >> >> For instance ThinLTOCodeGenerator::addModule is called >> through thinlto_codegen_add_module(). >> >> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check if >> it is fixed in Xcode 9? >> (I think I remember fixing it in ld64 but I'm not totally sure...). >> > > I haven't tried with Xcode 9. > > >> >> From w...
[ThinLTO] static library failure with object files with the same name
2017 Sep 18
2
[ThinLTO] static library failure with object files with the same name
...;>>>> >>>>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>>>> in llvm/tools/lto/lto.cpp) >>>>>> >>>>>> For instance ThinLTOCodeGenerator::addModule is called >>>>>> through thinlto_codegen_add_module(). >>>>>> >>>>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>>>> if it is fixed in Xcode 9? >>>>>> (I think I remember fixing it in ld64 but I'm not totally sure...). >>>>>&gt...
[ThinLTO] static library failure with object files with the same name
2017 Sep 18
0
[ThinLTO] static library failure with object files with the same name
...t;> Hi Johan, >>>>> >>>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>>> in llvm/tools/lto/lto.cpp) >>>>> >>>>> For instance ThinLTOCodeGenerator::addModule is called >>>>> through thinlto_codegen_add_module(). >>>>> >>>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>>> if it is fixed in Xcode 9? >>>>> (I think I remember fixing it in ld64 but I'm not totally sure...). >>>>> >>>> &...
[ThinLTO] static library failure with object files with the same name
2017 Sep 07
2
[ThinLTO] static library failure with object files with the same name
Hi Johan, ld64 only calls functions from llvm/include/llvm-c/lto.h (defined in llvm/tools/lto/lto.cpp) For instance ThinLTOCodeGenerator::addModule is called through thinlto_codegen_add_module(). Apple hasn't released the code for ld64 in Xcode 9 yet, did you check if it is fixed in Xcode 9? (I think I remember fixing it in ld64 but I'm not totally sure...). >From what I can see with Xcode 8.2, the linker just passes the file name (prefixed with the archive name): https://gi...
[ThinLTO] static library failure with object files with the same name
2017 Sep 06
3
[ThinLTO] static library failure with object files with the same name
On Wed, Sep 6, 2017 at 1:10 PM, Johan Engelen via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Tue, Sep 5, 2017 at 11:34 PM, Davide Italiano <dccitaliano at gmail.com> > wrote: >> >> On Tue, Sep 5, 2017 at 2:09 PM, Teresa Johnson <tejohnson at google.com> >> wrote: >> > >> > Hi Johan, >> > >> > Right, per the bug
[RFC] Embedded bitcode and related upstream (Part II)
2016 Jun 13
5
[RFC] Embedded bitcode and related upstream (Part II)
Thanks for the feedback! Replies inline. > On Jun 12, 2016, at 11:44 PM, Eric Christopher <echristo at gmail.com> wrote: > > Hi Steven, > > Great to see the commentary and updates here. I've got a few questions about some of this work. It might be nice to see some separate RFCs for a couple of things, but we'll figure that out after you send out patches probably :)