search for: llvc

...c code on the fly within my music application. Now I wish to use LLVM and GCC frontend as from what i can see it gives out good compiler warnings when you compile code where tiny c compiler does not. Is there a tutorial showing me how to compile c code on the fly within my c++ appliocation using LLVC and gcc frontend? or can LLVM not do this? thanks. -- View this message in context: http://old.nabble.com/LLVM-%2B-GCC-a-simple-tutorial-example--tp29425282p29425282.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc > > However, I am getting the following error. > > llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) The problem is most likely that sliceme2.cbc is *not* bytecode. Open the file and see. This message is checking for llvm or llvc (bytecode signature) in the first four bytes of the file. Its not finding it and reporting an error. > > How do I go about figuring out what the problem is? Edit the file (don't cat it, or you'll mess up your screen settings if it is bytecode). > llvmtest/sliceme2.cbc is newly...

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever

...an issue. Another issue that I have is that this is a very unix-centric solution. I guess that there isn't any good solution to this though. In principle, making the bc reader read your specially annotated .bc files shouldn't be an issue: it currently looks for a magic number for llvm/llvc files, and could check for a #! line as well. Instead of hard coding a fixed 256 byte offset, I don't see any reason the .bc reader couldn't skip ahead until it passes the first newline in the file. After the newline(s), it would start checking for llvm bc form. Does this make sense?...

...with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack using _alloca which caused the problem, because it felt that target was CygMing. Hacking the output of llvc-gcc from target triple="mingw32" to "win32" makes it "work". Is that generally dangerous, or should it be OK? I suppose I'll have to battle with msys/bison/m4 again, but they beat me soundly last time I tried to build mingw-lli. I tried to fix the alloca resolutio...

...9;s .ll, > and using an vcpp-built lli to run the resulting bytecode. This caused the > special case in X86RegisterInfo::emitPrologue for "main" to try to align the > stack using _alloca which caused the problem, because it felt that target > was CygMing. Hacking the output of llvc-gcc from target triple="mingw32" to > "win32" makes it "work". Is that generally dangerous, or should it be OK? I > suppose I'll have to battle with msys/bison/m4 again, but they beat me > soundly last time I tried to build mingw-lli. > > I tried to...

Hello, Scott. > Checking the assembly from llc, the first alloca call is to allocate > local vars in _main. Is this just the state of the code at 2.0 when > built with vs.net, or is there something that I've managed to > mis-build locally? _alloca is used to probe the stack, if you asks for locals of size more that 4k. This is pretty ugly, but the names of this functions differs

Karl, I think you meant to cc the llvmdev list on this. Thank you for a more detailed explanation, it's much clearer to me now. I agree that making the execution of .bc files more transparent would make it more useable as a stand-alone binary format on Unix-like systems and adding programmable support to changing the #! line would prevent much of user error involved in modifying the run

...mtest/sliceme2.cbc >> >> However, I am getting the following error. >> >> llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) > > The problem is most likely that sliceme2.cbc is *not* bytecode. Open the > file and see. This message is checking for llvm or llvc (bytecode > signature) in the first four bytes of the file. Its not finding it and > reporting an error. >> >> How do I go about figuring out what the problem is? > > Edit the file (don't cat it, or you'll mess up your screen settings if > it is bytecode). > &g...