similar to: [LLVMdev] How to do bitcode archive linking correctly?

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

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" is and these LTO mechanisms or where I can find further information? We used several

Hello everyone, I am a novice with KLEE under LLVM. I am trying to build a KLEE project (on a new LLVM environment) and I have the following problem: echo Testing... Testing... echo There should be no assertion fails! There should be no assertion fails! klee -taint=direct taint_direct.o KLEE: output directory = "klee-out-8" klee: error: Cannot find linker input

Hi, The klee library directory is determined at compile time and cannot be changed afterwards. Have a look at tools/klee/main.cpp to see how it is computed. I usually use Klee without any install step, right from the build directory. This has never given me the error you see. Hope this helps, Jonas On Wed, Jun 5, 2013 at 5:26 PM, Alexandru Ionut Diaconescu < alexandruionutdiaconescu at

On Thu, Feb 14, 2013 at 04:41:41PM -0800, Daniel Dunbar wrote: > Hi Tom, > > From the context I am assuming you are in a JIT context, so the comments > about 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? > Hi Daniel, I was using this code to

Hi Chris, What functions were you using, and what features of them were you using? If you just need to link individual bit codes together, you can do it in exactly the same way that llvm-link does (using Linker::LinkModules). If you really need features like being able to pull objects out of archives, then you should use an LTO enabled linker (either the system linker on OS X, or gold + the gold

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

Hi Philip, Thank you very much for your comments. I think I’ve discovered a root cause. The problem was in linking bit code archive files with the module. At some point, std::set<Module*> is used and iterated over. I believe this was the reason why e.g. It worked consistently with ASLR turned off and produced non-deterministic output otherwise. I changed that bit to use vector instead and

Looking at /tools/llvm-link/llvm-link.cpp may give you some ideas here. I havent looked at your specific use case, but llvm-link uses ParseIRFile to pull in a bitcode file and build a Module for it. You can then create a Composite using the Module * and call Linker::LinkModules(Composite.get(), NewModuleToLink.get()... to link a new Module to your Composite Module. -Chris On Feb 14, 2013, at

> Excuse me for the diversion but, is that interpreter of LLVM IR available > somewhere? Details on how it works, performance, etc? I'd be interested Yes it is available. The tool (KLEE [1]) is actually a lot more than an interpreter (although it can be used as one). KLEE allows you to mark certain variables (e.g. program inputs) as "symbolic". What this means is that the

On 20 December 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 >

Are there any "current" Linux distros that have installable packages for llvm, clang, nad klee? I am struggling to get klee built and need a working klee setup asap. Thanks in advance, Donald

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/tree/src/gallium/state_trackers/clover/llvm/invocation.cpp to work with TOT

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```

Hello, In my reading over the last couple of days, I have read that in order for klee to work with "native" Linux programs, I need to install the uClibc posix support for klee. I am not finding the uClibc source in the llvm svn repository anywhere. Is this still necessary for testing native Linux applications, and if so, where do I get the uClibc source to compile? Thanks in

Dear Developers, I am a Master's student at the ECE department of the University of Florida, USA.​​ For my research project, supervised by Prof. Mark Tehranipoor<http://tehranipoor.ece.ufl.edu/> and Prof. Farimah Farahmandi<http://farimah.ece.ufl.edu/>, I need to use Clang LLVM DataflowSanitizer library in KLEE. However, I have faced some difficulties (explained below) while

Hello, probably it is too late to be involved in GSoC, by I want discuss following idea: KLEE can generate tests only for main function level without any modifications of original code. It passes args specified by command line. I want implement automatic testcase generation for any imported function from tested code without its modification. First: parsing test code would collect input/output

When I try to execute the following example, I get an error message: /usr/local/lib/ruby/gems/1.8/gems/mocha-0.5.4/lib/mocha/object.rb:40: in `expects'': undefined method `stub'' for nil:NilClass (NoMethodError) from test8.rb:5 What could be the reason? I tried with the latest Mocha Ruby gem, and I also tried it with the Rails plugin. The example: require

Hi, I am trying to evaluate how complex would be to modify KLEE ( http://klee.llvm.org/ ) so that it can run LLVM bitcode compiled from Java code obtained with vmjc (from the VMKIT project). Your feedback will be very appreciated. I am familiar with KLEE but I would like to know more about VMKIT, so please point me to the right docs/source code if appropriate. After a quick look over

Hi, I'm using KLEE which supports only LLVM-2.9. In order to compile some c++ file which requires gcc 4.5, I built Dragonegg 2.9 with LLVM-2.9 and gcc 4.5.1 on a Linux x86_64 machine. It was sucessfully built. When I try to compile a c++ file using this plugin as below gcc test.cpp -fplugin=path/dragonegg.so I got this error: cc1plus: error: Cannot load plugin path/dragonegg.so