search for: machinemove

...assertions are disabled I get this error: llvm[1]: Compiling IntrinsicInst.cpp for Release-Asserts build In file included from IntrinsicInst.cpp:32: c:\mingw\bin\../lib/gcc/mingw32/4.3.0/include/c++/bits/ boost_concept_check.h: In instantiation of '__gnu_cxx::_SGIAssignableConcept<llvm::MachineMove>': c:\mingw\bin\../lib/gcc/mingw32/4.3.0/include/c++/bits/stl_vector.h: 179: insta ntiated from 'std::vector<llvm::MachineMove, std::allocator<llvm::MachineMove> > ' c:/Users/Greybird/Desktop/llvm/llvm-2.4/include/llvm/CodeGen/ MachineModuleInfo.h :1007: instantia...

Mark Kromis wrote: > Resend > > > On Oct 14, 2008, at 5:40 AM, Mark Kromis wrote: > > >> Greetings, >> >> I have a compiler error that I have not been able to get through. I >> usually depend upon pre-built binaries but there was none available >> for the pre-release. I also try scanning the web site and mail list >> but was unable to

...;d really appreciate some advice about this. I'm almost to the point where it's possible to use GCC-style exceptions under Win64, but I've hit a small roadblock. The problem is that I need information about what happens to the stack in the prologue. I know that information is stored in MachineMove objects in the MachineModuleInfo, but this information seems to be specific to DWARF CFI. Windows' scheme for storing information about the call frame differs somewhat from DWARF CFI. For one thing, the distinction between an x86 PUSH and MOV onto the stack is very important. Windows (and comp...

Hi Chip, > Because of all this, it's hard to reconstruct the SEH information from > the MachineMove array. I have thought about adding a new array specific > to SEH information, but I'm not sure how you guys would feel about that. > Any ideas on how to solve this problem? Same problem with ARM-specific EH. I ended with own information scheme, where instructions are marked as "frame...

...advice about this. I'm almost to the point where it's > possible to use GCC-style exceptions under Win64, but I've hit a small > roadblock. > > The problem is that I need information about what happens to the stack > in the prologue. I know that information is stored in MachineMove > objects in the MachineModuleInfo, but this information seems to be > specific to DWARF CFI. > > Windows' scheme for storing information about the call frame differs > somewhat from DWARF CFI. For one thing, the distinction between an x86 > PUSH and MOV onto the stack is ver...

On 11-06-02 6:56 AM, Anton Korobeynikov wrote: > Hi Chip, > >> Because of all this, it's hard to reconstruct the SEH information from >> the MachineMove array. I have thought about adding a new array specific >> to SEH information, but I'm not sure how you guys would feel about that. >> Any ideas on how to solve this problem? > Same problem with ARM-specific EH. I ended with own information > scheme, where instructions are mar...

On Jun 2, 2011, at 6:20 AM, Rafael Ávila de Espíndola wrote: > On 11-06-02 6:56 AM, Anton Korobeynikov wrote: >> Hi Chip, >> >>> Because of all this, it's hard to reconstruct the SEH information from >>> the MachineMove array. I have thought about adding a new array specific >>> to SEH information, but I'm not sure how you guys would feel about that. >>> Any ideas on how to solve this problem? >> Same problem with ARM-specific EH. I ended with own information >> scheme, where inst...

...Grosbach wrote: > > On Jun 2, 2011, at 6:20 AM, Rafael Ávila de Espíndola wrote: > >> On 11-06-02 6:56 AM, Anton Korobeynikov wrote: >>> Hi Chip, >>> >>>> Because of all this, it's hard to reconstruct the SEH information from >>>> the MachineMove array. I have thought about adding a new array specific >>>> to SEH information, but I'm not sure how you guys would feel about that. >>>> Any ideas on how to solve this problem? >>> Same problem with ARM-specific EH. I ended with own information >>> sc...

---------- Forwarded message ---------- From: Anton Korobeynikov <anton at korobeynikov.info> Date: Sun, Jun 5, 2011 at 11:20 Subject: Re: [LLVMdev] Advice on MachineMoves and SEH To: Charles Davis <cdavis at mymail.mines.edu> Chip, > Well, I've mulled it over for a while, and I've decided to take the ARM > EH approach of marking frame instructions and recognizing them later > during MachineInstr -> MCInst lowering. Given the trouble of...

Hi Devang, > How many passes are there this late in chain ? In any case, they all know how to deal with PROLOG_LABEL anyway. Personally, I'd like to make dwarf writer free of MachineModuleInfo. Quite a lot. Especially on ARM where we have all sorts of expansion and transformation passes at MI level. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint

Thx again Evan for the review. Here's a new patch for the JIT in itself. The major changes are: 1) A JITMemoryManager now has a flag saying "I require to know the size of what you want to emit" 2) DwarfJITEmitter is augmented with GetSize* functions 3) JITEmitter::startFunction checks if the JITMemoryManager requires to know the size. If so, it computes it and gives it through the

...Support/DataTypes.h" > +#include <string> > +#include <vector> > + > +namespace llvm { > + > +class Function; > +class MachineCodeEmitter; > +class TargetData; > +class TargetMachine; > +class MachineFunction; > +class MachineModuleInfo; > +class MachineMove; > +class MRegisterInfo; > + > +class DwarfEmitter { > +protected: > + /// BufferBegin/BufferEnd - Pointers to the start and end of the > memory > + /// allocated for this code buffer. > + unsigned char *BufferBegin, *BufferEnd; > + > + /// CurBufferPtr - Pointer...

Hi everyone, Here's a patch that enables exception handling when jitting. I've copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may need to factorize it, but the functionality is there and I'm very happy with it :) lli should now be able to execute the output from llvm-gcc when using exceptions (the UnwindInst instruction is not involved in this patch). Just add the

...;string> >> +#include <vector> >> + >> +namespace llvm { >> + >> +class Function; >> +class MachineCodeEmitter; >> +class TargetData; >> +class TargetMachine; >> +class MachineFunction; >> +class MachineModuleInfo; >> +class MachineMove; >> +class MRegisterInfo; >> + >> +class DwarfEmitter { >> +protected: >> + /// BufferBegin/BufferEnd - Pointers to the start and end of the >> memory >> + /// allocated for this code buffer. >> + unsigned char *BufferBegin, *BufferEnd; >>...

...-------= > ==// > + > +#ifndef LLVM_EXECUTION_ENGINE_JIT_DWARFEMITTER_H > +#define LLVM_EXECUTION_ENGINE_JIT_DWARFEMITTER_H > + > +namespace llvm { > + > +class Function; > +class MachineCodeEmitter; > +class MachineFunction; > +class MachineModuleInfo; > +class MachineMove; > +class MRegisterInfo; > +class TargetData; > +class TargetMachine; > + > +class JITDwarfEmitter { > + const TargetData* TD; > + MachineCodeEmitter* MCE; > + const MRegisterInfo* RI; > + MachineModuleInfo* MMI; > + JIT& Jit; > + bool needsIndirectEncodin...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL:

...a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols: "llvm::TargetRegisterInfo::getInitialFrameState(std::vector<llvm::MachineMove, std::allocator<llvm::MachineMove> >&) const", referenced from: vtable for llvm::EBCRegisterInfoin libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o) vtable for llvm::EBCGenRegisterInfoin libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o) "llvm::TargetMachine::getAsmVerbosityDe...

...a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols: "llvm::TargetRegisterInfo::getInitialFrameState(std::vector<llvm::MachineMove, std::allocator<llvm::MachineMove> >&) const", referenced from: vtable for llvm::EBCRegisterInfoin libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o) vtable for llvm::EBCGenRegisterInfoin libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o) "llvm::TargetMachine::getAsmVerbosityDe...