similar to: [LLVMdev] 64-bit lli can't run 32-bit bitcode?

Resending, any pointers? I demangled the symbol and it turns out to be: std::__1::locale::use_facet(std::__1::locale::id&) const tia, ashok On 5/19/2012 9:41 PM, Ashok Nalkund wrote: > Hi, > LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm > trying to load/execute using lli as below but it reports an error about > unresolved symbol: >> LLVM

Just forwarding it to the list. On Wed, Sep 21, 2011 at 10:43 PM, Taemin Kim <taemin0712 at gmail.com> wrote: > It works. =) Thank you very much. > Taemin > > On Wed, Sep 21, 2011 at 6:16 PM, Douglas do Couto Teixeira > <douglasdocouto at gmail.com> wrote: >> >> You can run the instnamer pass. So all instructions will get a name. >> >> I hope it

Hi, LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm trying to load/execute using lli as below but it reports an error about unresolved symbol: > LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! > lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54:

Ashok Nalkund wrote: > Resending, any pointers? I demangled the symbol and it turns out to be: > std::__1::locale::use_facet(std::__1::locale::id&) const My guess is that you've got a .bc file produced on a mac using libc++ (hence the ::_1 part) and you're trying to run it on linux with libstdc++ (which doesn't use inline namespaces, the '::_1::' part). That

Hi Nick, > Fundamentally the issue is that the system linker is supposed to define > __dso_handle when linking, but since there is no system linker between > your build of the .bc files and running lli, nobody has defined it. > > It seems reasonable to me that lli should define __dso_handle if it's > declared in the module. > > You could module tools/lli/lli.cpp to add

Ashok Nalkund wrote: > > Resending :(. Any pointers? Fundamentally the issue is that the system linker is supposed to define __dso_handle when linking, but since there is no system linker between your build of the .bc files and running lli, nobody has defined it. It seems reasonable to me that lli should define __dso_handle if it's declared in the module. You could module

Hi, This is probably an easy question, but I could not find the answer to it. I'm working on a LLVM back-end for the EHC compiler (a Haskell compiler). Currently there is a C back-end and I would like to reuse the primitive library functions from this back-end. So I have compiled C sources in a .o file and I would like to call these from my LLVM code. If I declare these primitive functions

Hi; Both -fplugin-arg-dragonegg-emit-ir and -flto works for creating llvm bitcode that can be run with lli. Thanks to Nick for the suggestion. Now, trying to run an OpenMP hello world program. llvm-gcc -fopenmp p_hello.c -flto -S -o p_hello.ll lli p_hello.ll output: LLVM ERROR: Program used external function 'GOMP_parallel_start' which could not be resolved! I am guessing that I have

Hello; I was writing this instrumentation pass and I am facing a problem. My pass instruments the bit code with some extra instructions. When I run this instrumented bitcode using lli, it runs perfectly, but when I compile the bitcode using llc and then produce the native binary using gcc and run it, I get a seg-fault. Can anyone please tell me the possible reason(s) for this? Thank you; --

On Saturday 11 of February 2012 14:29:10 Paweł Sikora wrote: > Hi, > > afaics in manuals the llvm-{link,ld} tools only can merge bitcode files > into one bigger piece which looks like a static-linking from the c/c++ world. > i'm wondering is it any possibility to link bitcode elements dynamically > in the same way as e.g. c#/msil assemblies? static linking into one

Hi all, I am in the process of developing a installer utility for ARM target which can compile any source files to ARM native executable. This installer utility should be present on target itself (whether this is feasible or not?). For achieving this i compiled llvm with clang for target. I copied the binaries to target and when it tried to compile a sample c code i am getting the following

Hi, I am trying to parallize the lli interpreter (code: http://pastebin.com/6iuHNH3Q). I am using ubuntu 12.04 with llvm version 3.1. Each thread uses a seperate LLVMContext, however the interpreter continues to crash. Error msg: ..../include/llvm/Support/Mutex.h:116: bool llvm::sys::SmartMutex<true>::release(): Assertion `((recursive && acquired) || (acquired == 1)) &&

Hello, I am generating profile_rt.dll by perfoming 'make' in $LLVM_SRC_DIR/runtime/libprofile. After make, I got the following error messages. llvm[0]: Linking Debug+Asserts Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:/cygdrive/c/ llvm/runtime/libprofile/Debug+Asserts/exported_symbols.lst: file format not reco gnized; treating as

Hi Xiaolong, > As Duncan described, "lli -load=libstdc++.dylib ..." works. I, > however, encounted an "Illegal instruction" message, while I was > trying to interpret a large program. are you using the interpreter or the JIT? So, does lli have a debug switch > for dumping out the details for errors? > > Using llc is not that simple, and I have not gotten

On Fri, Jun 4, 2010 at 1:09 AM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: > Hi Eli, > > I have attached a tar file containing Pass (ConditionPass.cpp), External > function (PrintRes.cpp) and test program (try.c). I use command chain as > describe in previous mail. Can you just attach the final program.bc you pass to lli? I don't know how to build a plugin off the top of

Works for me: [jhereg:~/tmp] echristo% /Volumes/Data/builds/build-llvm/Debug+Asserts/bin/clang -S -emit-llvm foo.cpp [jhereg:~/tmp] echristo% lli foo.s testing [jhereg:~/tmp] echristo% llvm-gcc -S -emit-llvm foo.cpp [jhereg:~/tmp] echristo% lli foo.s testing the first is using top of tree clang. The second is using an llvm-gcc on my OS. What versions are you using? -eric On Feb 6, 2012, at

Hello Everyone, I can cross-compile LLVM-2.5 to ARM and run lli on a simulator in debug mode . However, when I now compile with optimization enabled, lli triggers an assertion when loading bitcode files. The assertion looks like this : lli: /home/Virement/llvm/llvm-2.5-linux/include/llvm/Support/Casting.h:199: typename llvm::cast_retty<To, From>::ret_type llvm::cast(const Y&) [with X

Hi Xialong, > I have a program that uses C++ STL a lot. To have the source code for > STL functions, I undefined "_GLIBCXX_EXTERN_TEMPLATE" in > c++config.h. In spite of this, after compilation (via clang) and > linking (via llvm-ld), the resulting bitcode contains a few declared > functions (with no definitions). > > My question is: In the scenario where some

Hi Duncan, thanks for the answer. But "opt -load ..../Decorator.so -dec <prog.bc> new_prog.bc" creates an invalid file. When i use "lli", i get "lli: error loading program 'new_prog.bc': Invalid bitcode signature" I have done the followings: 1) used "opt -p -load ..../Decorator.so -dec <prog.bc> new_prog.bc" 2) copied the output

Thanks Duncan and Ashok, As Duncan described, "lli -load=libstdc++.dylib ..." works. I, however, encounted an "Illegal instruction" message, while I was trying to interpret a large program. So, does lli have a debug switch for dumping out the details for errors? Using llc is not that simple, and I have not gotten through the compilation process. For instance, "llc -o