search for: r172749

Hi, We're currently upgrading KLEE to work with LLVM >=3.3 and we've hit a problem. It seems r172749 removed support for linking a bitcode archive into a module. KLEE unfortunately depends on this to link in its runtime ( which amongst other things provides a C library [5] ). A first attempt at linking in a bitcode archive ourselves can be seen in [1]. This approach does not work correctly, it...

r172749 removed Linker/LinkArchives.cpp and Linker/LinkItems.cpp citing: This code is dead, and the "right" way to get this support is to use the platform-specific linker-integrated LTO mechanisms, or the forthcoming LLVM linker. Could someone please expand on what the "right way&qu...

Hi Daniel, In r172749 you removed the Linker::LinkInFiles() function and mentioned in the commit message that users of this function should migrate to "platform-specific linker-integrated LTO mechanisms, or the forthcoming LLVM linker." I'm trying to update this code: http://cgit.freedesktop.org/mesa/mesa...

On Tue, Dec 17, 2013 at 10:31:31AM +0000, Daniel Liew wrote: > Hi, > > We're currently upgrading KLEE to work with LLVM >=3.3 and we've hit a problem. > > It seems r172749 removed support for linking a bitcode archive into a > module. KLEE unfortunately depends on this to link in its runtime ( > which amongst other things provides a C library [5] ). > > A first attempt at linking in a bitcode archive ourselves can be seen in [1]. > > This approa...

...bitcode file. I would compile and OpenCL C kernel to bitcode and then link it with an OpenCL C builtin library which was also a bitcode file. -Tom > > > On Wed, Feb 13, 2013 at 12:24 PM, Tom Stellard <tom at stellard.net> wrote: > > > Hi Daniel, > > > > In r172749 you removed the Linker::LinkInFiles() function and mentioned > > in the commit message that users of this function should migrate to > > "platform-specific linker-integrated LTO mechanisms, or the forthcoming > > LLVM linker." > > > > I'm trying to update...

...out using a platform specific LTO mechanism don't apply. Were you using this code to extract bitcode files from archives, or just to link in an individual bitcode file? - Daniel On Wed, Feb 13, 2013 at 12:24 PM, Tom Stellard <tom at stellard.net> wrote: > Hi Daniel, > > In r172749 you removed the Linker::LinkInFiles() function and mentioned > in the commit message that users of this function should migrate to > "platform-specific linker-integrated LTO mechanisms, or the forthcoming > LLVM linker." > > I'm trying to update this code: > > htt...

Hi Rafael and other LLVM devs, I'm currently upgrading a project that uses LLVM that links a bitcode archive (a C library) with a module. Originally we used Linker::LinkInFile() but that was removed by r172749. So I started looking for an alternative and I found Archive::findModulesDefiningSymbols() which looked very promising as it would allow me to very easily implement linking a bitcode archive with a module efficiently (i.e. only call Linker::LinkModules() on the relevant bitcode modules inside the b...

...to bitcode and then link it with an OpenCL C > builtin library which was also a bitcode file. > > -Tom > > >> >> >> On Wed, Feb 13, 2013 at 12:24 PM, Tom Stellard <tom at stellard.net> wrote: >> >>> Hi Daniel, >>> >>> In r172749 you removed the Linker::LinkInFiles() function and mentioned >>> in the commit message that users of this function should migrate to >>> "platform-specific linker-integrated LTO mechanisms, or the forthcoming >>> LLVM linker." >>> >>> I'm...

...O enabled linker (either the system linker on OS X, or gold + the gold plugin on Linux). See also: http://llvm.org/docs/LinkTimeOptimization.html http://llvm.org/docs/GoldPlugin.html - Daniel On Tue, Jan 29, 2013 at 11:31 AM, Chris Cadwallader <ccadwallader at arxan.com>wrote: > r172749 removed Linker/LinkArchives.cpp and Linker/LinkItems.cpp citing: > > This code is dead, and the "right" way to get this support is to use the > platform-specific linker-integrated LTO mechanisms, or the forthcoming LLVM > linker. > > Could someone please expand on...

...2013 05:39, Daniel Liew <daniel.liew at imperial.ac.uk> wrote: > Hi Rafael and other LLVM devs, > > I'm currently upgrading a project that uses LLVM that links a bitcode > archive (a C library) with a module. Originally we used > Linker::LinkInFile() but that was removed by r172749. So I started > looking for an alternative and I found > Archive::findModulesDefiningSymbols() which looked very promising as > it would allow me to very easily implement linking a bitcode archive > with a module efficiently (i.e. only call Linker::LinkModules() on the > relevant bit...

...ew <daniel.liew at imperial.ac.uk> wrote: >> Hi Rafael and other LLVM devs, >> >> I'm currently upgrading a project that uses LLVM that links a bitcode >> archive (a C library) with a module. Originally we used >> Linker::LinkInFile() but that was removed by r172749. So I started >> looking for an alternative and I found >> Archive::findModulesDefiningSymbols() which looked very promising as >> it would allow me to very easily implement linking a bitcode archive >> with a module efficiently (i.e. only call Linker::LinkModules() on the &...