similar to: [LLVMdev] lli --force-interpreter does not find external function

Nick Lewycky <nicholas at mxc.ca> writes: > The interpreter uses libffi to make external function calls. However, it > needs to be detected at LLVM's compile time. If you're using the > released packages, we disabled that because we were worried about users > who don't have libffi installed. This seems to be quite a common problem (I too hit it once, thought it

Hi Nick: The first problem have been solved by calling llvm-ld: $ llvm-ld -o hellosin.llvm hellosin.bc -lm $ lli -force-interpreter=true -load=/usr/lib/libm.so hellosin.llvm.bc hello sin: 0.50 The pthread problem remains after llvm-ld: $ lli -force-interpreter=true -load=/lib/libpthread.so.0 phello.llvm.bc 0 lli 0x08796bf8 Segmentation fault For those who are getting "invalid

Hi Nick: Thanks for pointing me to libffi. Recompile LLVM with libffi does solve the problem of printf. But it still has other problems: 1) sinf() returns 0 in the interpreter, but returns correct value in JIT (see hellosin.c) 2) calling pthread_create cause lli to crash in the interpreter mode, but no problem in JIT (see phello.c). My questions are: i) can I call any arbitrary external function

Timo Juhani Lindfors wrote: > Nick Lewycky<nicholas at mxc.ca> writes: >> The interpreter uses libffi to make external function calls. However, it >> needs to be detected at LLVM's compile time. If you're using the >> released packages, we disabled that because we were worried about users >> who don't have libffi installed. > > This seems to be

Hi Nick: Thanks for the response. You are right about sinf. I changed the constant to sscanf(argv[1], ...), and it gave me back 0 again. I also compared the disassembled code, and saw it was indeed the case. The primary reason I use interpreter is because I wish to do runtime checking on memory access pattern in multithreaded C programs. for example, if thread one is in the critical section, I

Xu Yang wrote: > Hi: > > When I try to execute lli -force-interpreter=true hello.bc, it gave the > following error: > > LLVM ERROR: Tried to execute an unknown external function: i32 (i8*)* puts > > I think the error is because C library is not being linked with the byte > code, but I was not able to find any helpful instruction in lli's document. > > Can you

Xu Yang wrote: > Hi Nick: > > The first problem have been solved by calling llvm-ld: > > $ llvm-ld -o hellosin.llvm hellosin.bc -lm > $ lli -force-interpreter=true -load=/usr/lib/libm.so hellosin.llvm.bc > hello sin: 0.50 Only because the optimizer saw sin(constant) and folded it away. The entire program became 'print constant string'. There is certainly a bug

Hi: When I try to execute lli -force-interpreter=true hello.bc, it gave the following error: LLVM ERROR: Tried to execute an unknown external function: i32 (i8*)* puts I think the error is because C library is not being linked with the byte code, but I was not able to find any helpful instruction in lli's document. Can you please teach me how to do it? Thanks Xu The hello.bc is

On Thu, Dec 31, 2009 at 2:26 AM, Heming Cui <heming at cs.columbia.edu> wrote: > Hi Eli, >     Thanks for your reply. If I add -force-interpreter to lli, then it seems > that it can not run external function like printf or malloc. Is there any > easy way to solve this problem? Does the LLVM configure find libffi? -Eli

Hi, > It seems llvm interpreter only supports a limited number of external > functions. fmod, in particular is not supported. any reason why it is not > supported ? > > "lli -force-interpreter test.bc > LLVM ERROR: Tried to execute an unknown external function: double (double, > double)* fmod > " You can check out the comments in

Hi Eli, Thanks for your reply. If I add -force-interpreter to lli, then it seems that it can not run external function like printf or malloc. Is there any easy way to solve this problem? On Wed, Dec 30, 2009 at 11:26 PM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Wed, Dec 30, 2009 at 7:53 PM, Heming Cui <heming at cs.columbia.edu> > wrote: > > Dear all, >

Hi all I compiled LLVM using ./configure --enable-assertions --enable-debug-runtime --enable-debug-symbols --enable-docs --enable-shared --enable-libffi --disable-optimized And then try to execute a .bc file using lli, ${LLVM_HOME}/Debug+Asserts/bin/lli -debug -force-interpreter ./jpegant.bc It reports : About to interpret: %9 = call i8* @memset(i8* %8, i32 0, i32 122)LLVM ERROR: Tried

Hi Eli, I think the llvm configure has already configured with ffi. ../llvm-2.6/configure -help | grep ffi --enable-libffi Check for the presence of libffi (default is YES) In addition, the printf() can work in program, reflecting that libffi is working, right? How can I make Interpreter work with getpid(), fork(), and clone()? On Thu, Dec 31, 2009 at 2:33 AM, Eli

On Jun 14, 2011, at 7:57 PM, 陳韋任 wrote: > Hi, > >> It seems llvm interpreter only supports a limited number of external >> functions. fmod, in particular is not supported. any reason why it is not >> supported ? >> >> "lli -force-interpreter test.bc >> LLVM ERROR: Tried to execute an unknown external function: double (double, >> double)* fmod

It seems llvm interpreter only supports a limited number of external functions. fmod, in particular is not supported. any reason why it is not supported ? "lli -force-interpreter test.bc LLVM ERROR: Tried to execute an unknown external function: double (double, double)* fmod " -- Kind Regards Xin Tong -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello > Is there additionnals information to provide to the linker when > compiling llvm on mac os x? Do you have libffi installed somehere? > > > The second question concerns Yellow Dog Distribution(6.2) on CellSPU > processor. Does lli support JIT compilation on CELL? No. As far as I can see, there is no JIT for SPU. -- With best regards, Anton Korobeynikov. Faculty of

How can I specify that LLVMInterpreter depends on 'libffi' in the Makefile? Modifying LD.Flags in Interpreter/Makefile doesn't help since llvm-config doesn't pick up on that, causing a linker error when building lli. I'd like "llvm-config --libs interpreter" return -lffi along with the LLVM libraries it lists. You'd think there would be an example of this

> > Is it turned ON in your build? > Yes it is turned on in my build here is my build script PATH=/mingw64/bin:$PATH FFI_INCLUDE_DIR="$(pkg-config --cflags libffi)" > FFI_INCLUDE_DIR=$(echo $FFI_INCLUDE_DIR | sed 's|-I||g') > > /mingw64/bin/cmake.exe \ > -G"MSYS Makefiles" \ > -DCMAKE_MAKE_PROGRAM="/usr/bin/make.exe" \ >

Hi, I'm yet working on the LLVM ExecutionEngine portability (2.6 release version) and I get two different problems depending on the platform. The first problem concerns compilation on MacOs X (10.5.5) with an X86 processor, when trying to compile my own project containing the ExecutionEngine class and the linker class. I get links problem with "_ffi_type_sint16",

Jerome: No, there are no plans to JIT to SPU. That's considerably more complicated -- you'd have to figure out when to JIT to the SPU and live with all of the constraints that the SPU imposes (data reformatting, r/w DMA, ensure your code lives in 256K unless you can manage to interface with the virtual I-cache work.) Basically, it's not trivial and it doesn't quite fit into the