similar to: [LLVMdev] Newbie JITter

On Nov 7, 2007, at 6:10 PM, Antony Blakey wrote: > Hi, > I'm experimenting with using LLVM to generate dynamic FFI bridges > in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from > dynamically generated assembler source to machine code, and I have > that all working, copied from the llc tool and the JIT example. I > have two questions: > > 1. What

Currently, the MachO and ELF Writers and MachineCodeEmitters are hard-coded into LLVMTargetMachine and llc. In other words, the 'object file generation' capabilities of the Common Code Generator are not generic. LLVMTargetMachine::addPassesToEmitFile explicitly checks whether the derived backend TargetMachine implements one of getMachOWriterInfo or getELFWriterInfo, and returns a

Hi folks, just installed the new llvm 1.9 build and noticed that my code no longer worked. It seems something has changed with addPassesToEmitFile(). First, the arguments to that method changed so that it no longer takes a PassManager, but only a FunctionPassManager. Instead there is a addPassesToEmitWholeFile() method, but that is marked as optional, and when I change my code to

> Currently, the MachO and ELF Writers and MachineCodeEmitters are > hard-coded into LLVMTargetMachine and llc. I am also interested in working on this area and interested in writting a COFF file backend. > In other words, the 'object file generation' capabilities of the > Common Code Generator are not generic. I was looking at making a parallel class to MachineCodeEmitter,

Hello, I'm not sure what I am trying to do is possible. I'm trying to create two modules, and call a function in one module from another module. First, a reassurance that I'm not trying to do something completely off the wall would be nice as I don't see any tutorials that do this. Second, any help getting this to work would be wonderful. Thanks, Aaron In my code, you'll

Sorry I forgot to add code that I use to run code: /* Executes the AST by running the main function */ GenericValue CodeGenContext::runCode() { std::cout << "Running code...\n"; ExecutionEngine *ee = EngineBuilder(module).create(); vector<GenericValue> noargs; GenericValue v = ee->runFunction(mainFunction, noargs); std::cout << "Code was run.\n"; return v;

On Sun, 21 Jan 2007, Marcel Weiher wrote: > just installed the new llvm 1.9 build and noticed that my code no > longer worked. It seems something has changed with > addPassesToEmitFile(). First, the arguments to that method changed so > that it no longer takes a PassManager, but only a > FunctionPassManager. Instead there is a addPassesToEmitWholeFile() > method, but that is

I like the idea of a generic MachineCodeWriter, although I prefer the name 'ObjectFileWriter'... I think we need to take a hard look at which bits of the Writer/Emitter infrastructure are needed for what tasks (Object File Emittion, JIT, etc.) and make sure that our abstractions are flexible enough... As it stands at the moment, the Writer and Emitter classes could definately be merged

On Jan 8, 2013, at 8:09 , Manuele Conti <manuele.conti at sirius-es.it> wrote: > Sorry I forgot to add code that I use to run code: > /* Executes the AST by running the main function */ > GenericValue CodeGenContext::runCode() { > std::cout << "Running code...\n"; > ExecutionEngine *ee = EngineBuilder(module).create(); > < > div

Dear list members, i have build a package which contains a collection of my frequently used functions. To keep the code organized I have broken down some rather extensive and long functions into individual steps and bundled these steps in sub-functions that are called inside the main function. To keep an overview over which sub-function belongs to which main function I saved all the respective

Antony Blakey wrote: > SVN head LLVM and Clang built out of the box for me a week ago on > MSYS/MINGW, using the following files: Ok, I tried to do the same. The compilations stops with the following error message (actually, I got to the same point in my attempt to build LLVM with the MinGW compiler shipped with Cygwin): llvm[1]: Compiling MachineLoopInfo.cpp for Debug build

Thanks Evan. On 09/11/2007, at 6:50 PM, Evan Cheng wrote: >> 1. What optimization passes, if any, should I run on the module >> before I pass it to the ExecutionEngine. > > The default JIt driver, lli, runs everything. My reading of the lli source indicates that it's not explicitly doing any opt passes - is that happening implicitly in the ExecutionEngine? I can see

On 24/11/2007, at 9:33 AM, John van Schie wrote: > Antony Blakey wrote: >> On 24/11/2007, at 12:01 AM, Michael T. Richter wrote: >> >>> Does anybody have a working version of LLVM 2.1+ (ideally in a .deb >>> file) that they're willing to share? I'm having some weird problems >>> trying to get a working version on my 7.10 machine. >>

Antony Blakey wrote: > On 24/11/2007, at 12:01 AM, Michael T. Richter wrote: > >> Does anybody have a working version of LLVM 2.1+ (ideally in a .deb >> file) that they're willing to share? I'm having some weird problems >> trying to get a working version on my 7.10 machine. > > Or even better, does anyone have a recipe for building on Gutsy? I've just

Hi all, With the newest patches to LLVM, there should be no reason for having "#include <iostream>" in any library source code file, except for lib/ Support/Streams.cpp. Please use the following instead: OLD NEW --- --- std::ostream llvm::OStream std::istream llvm::IStream std::cerr llvm::cerr std::cerr llvm::cout

Hello, I'm trying to catch assembly output and do some formatting for its presentation while being executed. I face a problem, which is clear from the error, although I have no clue on how to do it otherwise. If generating the code for its asm output and then for jit execution I get: ********** static llvm::MachineFunction& llvm::MachineFunction::construct(const llvm::Function*, const

When I try to print out a instruction by the following way, I am getting the error message below. Anyone knows what's the problem? Instruction* inst; ... inst-print(cerr); testbuild.cpp:178: error: no matching function for call to 'llvm::Instruction::print(llvm::OStream&)' /x/pchsu/llvm/llvm-2.4/include/llvm/Value.h:83: note: candidates are: void

On Tue, 17 Aug 2004, Reid Spencer wrote: > That's pretty cute actually. Do you want this "brilliant" :) example in the cvs > repository? I'd be happy to put it in. Here's an idea: how about we take the ModuleMaker, Valery's previous example, and this one and put them all in one "small examples" project? -Chris > Valery A.Khamenya wrote: > >

Does anybody have a working version of LLVM 2.1+ (ideally in a .deb file) that they're willing to share? I'm having some weird problems trying to get a working version on my 7.10 machine.

On 24/11/2007, at 12:01 AM, Michael T. Richter wrote: > Does anybody have a working version of LLVM 2.1+ (ideally in a .deb > file) that they're willing to share? I'm having some weird problems > trying to get a working version on my 7.10 machine. Or even better, does anyone have a recipe for building on Gutsy? Antony Blakey ------------- CTO, Linkuistics Pty Ltd Ph: 0438 840