search for: moduleutils

...t trivial. - According to LangRef, the third field is optional [1]. [1]: http://llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable - It was added in r209015 to support comdat keys. - The helper functions `llvm::appendToGlobalCtors()` and `llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default set up the two-field version. - Despite the field being optional (and the API defaulting to the short version), the BitcodeReader auto-upgrades to the 3-element version. It looks to me like `@llvm.global_ctors` and `@llvm.global_dtors` are in an inconsistent sta...

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

...gt; > > > [1]: > http://llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable > > > > - It was added in r209015 to support comdat keys. > > > > - The helper functions `llvm::appendToGlobalCtors()` and > > `llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default > > set up the two-field version. > > > > - Despite the field being optional (and the API defaulting to the > > short version), the BitcodeReader auto-upgrades to the 3-element > > version. > > > > It looks to me like `@ll...

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

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*

> On May 25, 2016, at 6:05 AM, Pierre Gagelin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi everyone, > > I am having troubles but this shouldn't be hard to solve for many people here. I am beginning a runtime feature for the BoundsChecking pass and I want to replace the libc malloc&free. I followed the design of AddressSanitizer (Asan) and tried to use the

...//llvm.org/docs/LangRef.html#the-llvm-global-ctors-global-variable >>>> >>>> - It was added in r209015 to support comdat keys. >>>> >>>> - The helper functions `llvm::appendToGlobalCtors()` and >>>> `llvm::appendToGlobalDtors()` (in ModuleUtils.cpp) will by default >>>> set up the two-field version. >>>> >>>> - Despite the field being optional (and the API defaulting to the >>>> short version), the BitcodeReader auto-upgrades to the 3-element >>>> version. >>>...

Hi everyone, I am having troubles but this shouldn't be hard to solve for many people here. I am beginning a runtime feature for the BoundsChecking pass and I want to replace the libc malloc&free. I followed the design of AddressSanitizer (Asan) and tried to use the INTERCEPTOR macro from the interception.h file of compiler-rt library. Here is the problem. The file I modify

...piling Mem2Reg.cpp for Release+Asserts build llvm[2]: Compiling Lint.cpp for Release+Asserts build llvm[3]: Building X86.td disassembly tables with tblgen llvm[3]: Compiling MetaRenamer.cpp for Release+Asserts build llvm[3]: Compiling ScheduleDAGFast.cpp for Release+Asserts build llvm[3]: Compiling ModuleUtils.cpp for Release+Asserts build llvm[2]: Compiling Loads.cpp for Release+Asserts build llvm[3]: Compiling PromoteMemoryToRegister.cpp for Release+Asserts build llvm[3]: Building X86.td "fast" instruction selector implementation with tblgen llvm[2]: Compiling LoopAccessAnalysis.cpp for Relea...

...nclude "llvm/Analysis/AliasAnalysis.h" +#include "llvm/Target/TargetLowering.h" +#include "llvm/Target/TargetOptions.h" +#include "llvm/Target/TargetSubtargetInfo.h" +#include "llvm/Target/TargetFrameLowering.h" +#include "llvm/Transforms/Utils/ModuleUtils.h" +#include "llvm/Transforms/Utils/Local.h" +#include "llvm/ADT/Triple.h" +#include "llvm/ADT/Statistic.h" +#include "llvm/Support/Format.h" +#include "llvm/Support/raw_os_ostream.h" + +using namespace llvm; + +namespace llvm { + +STATISTIC(Nu...