similar to: [LLVMdev] lli problem in llvm

Hi, I'm using the JIT in LLVM version 1.9. It works fine, but when I try to use it with the interpreter enforced (using the -force-interpreter=true option) it seems to have trouble with the standard input and output streams (stdin, stdout, stderr). I get the following error when I try to run any application that uses one of these: "Could not resolve external global address:

Hi Reid, I am using llvmgcc4-1.9 for x86 linux, and I got my version of LLVM from CVS repository. Are these versions not compatible? Thanks, Joy. -- Joy W. Kamunyori Graduate Student - Computer Science Dept. University of Virginia jkamunyori at cs.virginia.edu "Life must be understood backwards; but... it must be lived forward." Soren Kierkegaard

Thank you. It works perfectly now. Joy. -- Joy W. Kamunyori Graduate Student - Computer Science Dept. University of Virginia jkamunyori at cs.virginia.edu "Life must be understood backwards; but... it must be lived forward." Soren Kierkegaard

Perhaps I missed something but I don''t see an easy way to do this ? Basically just wanna hold some ui state in a cookie. Did I miss something obvious ? Best Matt *********************************************************************************** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorized and

WINE 1.1.18 has a regression from WINE 1.1.14. Once again, GP4 no longer installs from CD... the console outputs the following ole error repeatedly: err:ole:xCall Failed to serialize param, hres 80040155 err:ole:deserialize_param Failed to read integer 4 byte err:ole:TMStubImpl_Invoke Failed to deserialize param State, hres 80004005 err:rpc:I_RpcReceive we got fault packet with status 0x80004005

I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page. I made hello.c file exactly same shown in the page. I made hello.bc on UNIX and transferred it to my Windows computer. And I typed "llc -march=c hello.bc" (Of course, I downloaded the latest version of LLVM and compiled with VS before this.) But my command

On Apr 27, 2013, at 8:10 AM, Chandler Carruth <chandlerc at google.com> wrote: > On Fri, Apr 26, 2013 at 11:33 PM, Dan Gohman <dan433584 at gmail.com> wrote: > To all, I'm moving on and accepting what appears to be the consensus of the list, for now. > > I want to point out something about this direction that hasn't really come up, but I think deserves some better

Hello, I was trying to use lli to run a very simple c++ program on linux that uses the c++ library but the interpreter crashed. But the same works fine with JIT enabled. I am wondering if anyone has encountered similar issues? Thanks, Alvin ------------------------------------------------------------------------------- #include <string> void main() { std::string

Hi Armin, Argument parsing isn't handled by the JIT. This sounds like you're making redundant calls to cl::ParseCommandLineOptions ? Deleting the ExecutionEngine and any RTDyldMemoryManager instances that you've created should be enough to reset the JIT. Cheers, Lang. On Tue, Jan 20, 2015 at 12:38 PM, Armin Steinhoff <armin at steinhoff.de> wrote: > > Hi, > >

Jello Juan, The interpreter is quite useless in its current state. Try using a JIT compiler for you computer from the lli command and it should work. --Sam > >From: Juan Carlos Martinez Santos <juanc.martinez.santos at gmail.com> >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >Sent: Thursday, June 25, 2009 1:04:17 PM >Subject: [LLVMdev] Problems with lli

Hi, Using the trunk of svn. I'm trying to get inline-asm working on X86. So I added call to: > InitializeNativeTargetAsmParser() during initialization. However, this causes a linking error: > llvm[2]: Linking Debug+Asserts executable lli > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function

Hi, Is it normal/expected for `llc` to support a different set of targets than `lli`? I have a hello.ll on which this works: $ llc -mtriple=armv7a-linux-gnueabihf hello.ll # OK, generates hello.s But this doesn't: $ lli -mtriple=armv7a-linux-gnueabihf hello.ll # lli: error creating EE: No available targets are compatible with this triple, see -version for the available targets. I'm

Linking lli debug executable (without symbols) /mounts/zion/disks/0/localhome/pmeredit/llvm/lib/Debug/lli-interpreter.o(.te xt+0x643a): In function `llvm::Interpreter::callExternalFunction(llvm::Function*, std::vector<llvm::GenericValue, std::allocator<llvm::GenericValue> > const&)': /localhome/pmeredit/llvm/lib/ExecutionEngine/Interpreter/ExternalFunctions.c pp:98: undefined

Hello, I just install the new newest version of LLVM. When I ran the hello.c example I got the below message. Somebody has an idea what is wrong? The problem is just with lli, the other commands worked as I expected. ********************** :~/LLVM/my-test$ lli hello.bc Tried to execute an unknown external function: i32 (i8*)* puts 0 lli 0x0861fab8 Stack dump: 0. Program arguments: lli

I get the following error when I try to run arm lli on QEMU: lli: llvm-arm/src/llvm/include/llvm/ADT/ilist.h:197: typename bidirectional_iterator<NodeTy, int>::reference llvm::ilist_iterator<NodeTy>::operator*() const [with NodeTy = llvm::RecyclerStruct]: Assertion `Traits::getNext(NodePtr) != 0 && "Dereferencing end()!"' failed. 0 lli 0x006abbfc Stack dump: 0.

When you run a program foo linked with gccld (i.e., by running the script "foo" it outputs which runs lli) it passes foo.bc instead of foo as the argv[0] for the program. This is surprising to the user, who is expecting that a program started by running "./foo" will call itself "./foo", not "./foo.bc". Fixed by removing ".bc" from the end of

hannibal hannibal wrote: > I get the following error when I try to run arm lli on QEMU: > > lli: llvm-arm/src/llvm/include/llvm/ADT/ilist.h:197: typename bidirectional_iterator<NodeTy, int>::reference llvm::ilist_iterator<NodeTy>::operator*() const [with NodeTy = llvm::RecyclerStruct]: Assertion `Traits::getNext(NodePtr) != 0 && "Dereferencing end()!"'

On Oct 18, 2009, at 6:32 PM, Eric Brunstad wrote: > Hi, > > Is it possible to run Objective-C code in lli? lli does not seem to > want to load Foundation.framework. It is definitely possible, but we're not there yet. LLI would have to know about objective-c metadata to register it properly with the runtime. This is important for things like classes etc. This isn't

Where do I add that line? Just putting it in the vanilla Makefile in tools/lli doesn't work. ----- Original Message ----- From: "Reid Spencer" <reid at x10sys.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Thursday, February 24, 2005 6:50 PM Subject: Re: [LLVMdev]Linker error building (modified) lli >

Hi, What is mklib trying to do with lli.exe.exp? However, lli.exe gets linked anyway. -------------- llvm[2]: Linking Debug executable lli /C/projects/build/MinGW/llvm-1-1/mklib: /C/projects/build/MinGW/llvm-1-1/Debug/bin/.libs//C/projects/build/MinGW/llvm-1-1/Debug/bin/lli.exe.exp: No such file or directory llvm[2]: ======= Finished Linking Debug Executable lli -------------- Henrik.