similar to: [LLVMdev] [LLVM] What has happened to LLVM bitcode archive support?

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

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

Hi all, I'm new to llvm and klee. Now I'm trying to build up coreutil with klee. Following the steps online (http://klee.llvm.org/TestingCoreutils.html), I went to step 3 and stuck. When I try to run: klee --libc=uclibc --posix-runtime ./cat.bc -version Error occurred like: klee: error: Cannot find linker input '/lib/libc.a' klee: ModuleUtil.cpp:42: llvm::Module*

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

On Sat, Mar 16, 2013 at 06:16:01AM -0700, Hongxu Chen wrote: > Thanks for your help, Wei-Ren and Anton. > > However since I am doing some experiments with klee(http://klee.llvm.org/ > GetStarted.html) and llvm-gcc seems to have better compatibility with it. So I > still hope that I can use llvm-gcc:-) Seems you already found the answer on klee ML. :) Regards, chenwj --

Thanks for your help, Wei-Ren and Anton. However since I am doing some experiments with klee( http://klee.llvm.org/GetStarted.html) and llvm-gcc seems to have better compatibility with it. So I still hope that I can use llvm-gcc:-) Hongxu Chen On Sat, Mar 16, 2013 at 3:35 PM, 陳韋任 (Wei-Ren Chen) [via LLVM] < ml-node+s1065342n56013h94 at n5.nabble.com> wrote: > Hi Chen, > >

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

Hi I need a concolic execution framework based on LLVM. As far as I know, KLEE might be the best choice. However, KLEE(the stable version) is based on LLVM 3.4. I compiled my code with the latest LLVM, whose version is 7.0. Anyone know whether the bitcode could be used by KLEE. Or do I have to compile with the old version of LLVM again. Furthermore, if you have any other concolic execution

On Mon, 18 Jun 2012 15:15:13 MDT, Richard <legalize at xmission.com> wrote: > Does anyone recall the specific paper/system so that I can revisit it? Of course, I stumble across it as soon as I posted the message... KLEE is what I was remembering: <http://klee.llvm.org/GetStarted.html> -- "The Direct3D Graphics Pipeline" free book

Hi, I'm working on a tool (KLEE) that interprets LLVM bitcode. One of the things it does is it instruments the LLVM bitcode with checks for division by zero. It does this by injecting calls to a function "klee_div_zero_check(long long divisor)" just before every division instruction (e.g. SDiv). These checks are injected by a pass that has been implemented in KLEE. This

> I would suggest for now building the archive with gnu ar and the > plugin, that way you have an index and don't need to read all members. Thanks for the suggestion.I'll check out [1]. It would be definitely be faster using LLVMGold.so with ar but to be honest I'd rather take a small performance hit but make life much easier for our users at the moment because the build process

>> Therefore LLVM is still supporting runtime libraries that consist of llvm >> bitcode files (even if the format is now different) > > runtime? It is still possible to build .a files if that is what you men. Sorry I haven't explained very clearly. The tool that I work on is an interpreter of LLVM IR and when the tool runs, it links in an archive of bitcode modules into the

Hi Rafael, On 20 Dec 2013, at 14:30, Rafael Espíndola wrote: > 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

> We are going this way, yes. You've confused me a bit here ( maybe I was being too vague ) Okay so I understand thst the old LLVM specific archive format is now gone. However it seems you are allowing LLVM bitcode files ( I assume that's what you mean by "IL" - does that stand for "intermediate language"? It's not in [1] ) to be placed inside the more

Hi, The llvm-gcc binaries I downloaded for the 2.7 prerelease contained a .la for libstdc++, and a .a file, but no .so file: /home/edwin/llvm2.7/llvm-gcc-4.2-2.7-x86_64-linux/lib64/libstdc++.la /home/edwin/llvm2.7/llvm-gcc-4.2-2.7-x86_64-linux/lib64/libstdc++.a While testing libtool's new LTO support [1] everything broke when it tried to use that .la file, with millions of messages like

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 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, 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

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