search for: emitalign

Hi everyone, vmkit requires to know the size of a jitted method before emitting the method. This allows to allocate the correct size for the method. The attached patch creates this functionality when the flag SizedMemoryCode is on. In order to implement this functionality, i had to virtualize some MachineCodeEmitter functions. Is it OK to commit the patch? Thanks, Nicolas --------------

...fo(MachineJumpTableInfo *MJTI); >> + >> + >> + virtual void startFunction(MachineFunction &F) { >> + CurBufferPtr = 0; >> + Fn = &F; >> + >> + // Ensure the constant pool/jump table info is at least 4-byte >> aligned. >> + emitAlignment(16); >> + >> + initConstantPool(F.getConstantPool()); >> + initJumpTableInfo(F.getJumpTableInfo()); >> + >> + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + >> CurBufferPtr); >> + JumpTableBase = (void*)(((uintptr_t) Jump...

...> + > + void initJumpTableInfo(MachineJumpTableInfo *MJTI); > + > + > + virtual void startFunction(MachineFunction &F) { > + CurBufferPtr = 0; > + Fn = &F; > + > + // Ensure the constant pool/jump table info is at least 4-byte > aligned. > + emitAlignment(16); > + > + initConstantPool(F.getConstantPool()); > + initJumpTableInfo(F.getJumpTableInfo()); > + > + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + > CurBufferPtr); > + JumpTableBase = (void*)(((uintptr_t) JumpTableBase) + > CurBuffe...

...t;>> + >>> + >>> + virtual void startFunction(MachineFunction &F) { >>> + CurBufferPtr = 0; >>> + Fn = &F; >>> + >>> + // Ensure the constant pool/jump table info is at least 4-byte >>> aligned. >>> + emitAlignment(16); >>> + >>> + initConstantPool(F.getConstantPool()); >>> + initJumpTableInfo(F.getJumpTableInfo()); >>> + >>> + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + >>> CurBufferPtr); >>> + JumpTableBase =...

...>>>> + virtual void startFunction(MachineFunction &F) { >>>> + CurBufferPtr = 0; >>>> + Fn = &F; >>>> + >>>> + // Ensure the constant pool/jump table info is at least 4-byte >>>> aligned. >>>> + emitAlignment(16); >>>> + >>>> + initConstantPool(F.getConstantPool()); >>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>> + >>>> + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + >>>> CurBufferPtr); >>>&...

...t;>>>>> + CurBufferPtr = 0; >>>>>> + Fn = &F; >>>>>> + >>>>>> + // Ensure the constant pool/jump table info is at least 4- >>>>>> byte >>>>>> aligned. >>>>>> + emitAlignment(16); >>>>>> + >>>>>> + initConstantPool(F.getConstantPool()); >>>>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>>>> + >>>>>> + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + >&...

...+ CurBufferPtr = 0; >>>>>>> + Fn = &F; >>>>>>> + >>>>>>> + // Ensure the constant pool/jump table info is at least 4- >>>>>>> byte >>>>>>> aligned. >>>>>>> + emitAlignment(16); >>>>>>> + >>>>>>> + initConstantPool(F.getConstantPool()); >>>>>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>>>>> + >>>>>>> + ConstantPoolBase = (void*)(((uintptr_t) &gt...

...MachineFunction &F) { >>>>> + CurBufferPtr = 0; >>>>> + Fn = &F; >>>>> + >>>>> + // Ensure the constant pool/jump table info is at least 4- >>>>> byte >>>>> aligned. >>>>> + emitAlignment(16); >>>>> + >>>>> + initConstantPool(F.getConstantPool()); >>>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>>> + >>>>> + ConstantPoolBase = (void*)(((uintptr_t) ConstantPoolBase) + >>>>> CurB...

...gt;>>>>>>> + Fn = &F; >>>>>>>> + >>>>>>>> + // Ensure the constant pool/jump table info is at least 4- >>>>>>>> byte >>>>>>>> aligned. >>>>>>>> + emitAlignment(16); >>>>>>>> + >>>>>>>> + initConstantPool(F.getConstantPool()); >>>>>>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>>>>>> + >>>>>>>> + ConstantPoolBase = (void*...

...gt;>>>>>> + >>>>>>>>> + // Ensure the constant pool/jump table info is at least >>>>>>>>> 4- >>>>>>>>> byte >>>>>>>>> aligned. >>>>>>>>> + emitAlignment(16); >>>>>>>>> + >>>>>>>>> + initConstantPool(F.getConstantPool()); >>>>>>>>> + initJumpTableInfo(F.getJumpTableInfo()); >>>>>>>>> + >>>>>>>>> + Consta...

...ive and value. > + /// > + void EmitInt64(uint64_t Value) { > + if (CurBufferPtr+8 <= BufferEnd) { > + *((uint64_t*)CurBufferPtr) = Value; > + CurBufferPtr += 8; > + } else { > + CurBufferPtr = BufferEnd; > + } > + } > + > + > + /// emitAlignment - Move the CurBufferPtr pointer up the the > specified > + /// alignment (saturated to BufferEnd of course). > + void EmitAlignment(unsigned Alignment) { > +// printf(".align %x\n", 1 << Alignment); > + if (Alignment == 0) Alignment = 1; > + // Mov...

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

Hi Duncan, > > I'm trying it on 4.0. On 4.2, I'm getting this problem during bootstrapping: > > > > ccAMeZbg.s:111:non-relocatable subtraction expression, > > "___gxx_personality_v0" minus "L0" > > ccAMeZbg.s:111:symbol: "___gxx_personality_v0" can't be undefined in a > > subtraction expression > > this is the

...he target in case no attributes are specified for a function. "An explicit alignment may be specified for a function. If not present, or if the alignment is set to zero, the alignment of the function is set by the target to whatever it feels convenient.” So, as a first try, I dived into the “EmitAlignment” code in AsmPrinter.cpp and simply removed the function alignment part. Interestingly the compilation seems flawless at many cases (large programs) but on a few programs, it produces a segfault-generating executable. So my guess is that for some functions, alignment is necessary for soundness,...

...EmitInt64(uint64_t Value) { >> + if (CurBufferPtr+8 <= BufferEnd) { >> + *((uint64_t*)CurBufferPtr) = Value; >> + CurBufferPtr += 8; >> + } else { >> + CurBufferPtr = BufferEnd; >> + } >> + } >> + >> + >> + /// emitAlignment - Move the CurBufferPtr pointer up the the >> specified >> + /// alignment (saturated to BufferEnd of course). >> + void EmitAlignment(unsigned Alignment) { >> +// printf(".align %x\n", 1 << Alignment); >> + if (Alignment == 0) Alignment =...

Hi Bill, > I'm trying it on 4.0. On 4.2, I'm getting this problem during bootstrapping: > > ccAMeZbg.s:111:non-relocatable subtraction expression, > "___gxx_personality_v0" minus "L0" > ccAMeZbg.s:111:symbol: "___gxx_personality_v0" can't be undefined in a > subtraction expression this is the darwin assembler that barfs, right? It

...sizeof(int8_t) + // TType format > + AsmPrinter::SizeULEB128(TypeOffset) + // > TType base offset > + TypeOffset; > + > + unsigned SizeAlign = (4 - TotalSize) & 3; > + > + // Begin the exception table. > + MCE->emitAlignment(4); > + for (unsigned i = 0; i != SizeAlign; ++i) { > + MCE->emitByte(0); > + // Asm->EOL("Padding"); > + } > + > + unsigned char* DwarfExceptionTable = (unsigned char*)MCE- > >getCurrentPCValue(); > + > + // Emit the header. > + MCE-...

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:

I ran into a bug in this patch. The mapping symbol produced is aligned and it should not be. Is there a way to configure the MCSymbolRefExpr such that the emitted symbol is unaligned? Alternatively, should the ARM/Thumb code be realigned after a data-in-code section? I notice that GCC leaves it unaligned. Thanks, Greg On Wed, Oct 17, 2012 at 2:32 PM, Renato Golin <rengolin at

On 17 October 2012 22:23, Greg Fitzgerald <garious at gmail.com> wrote: > I had to move MCELF.h to "include/llvm/MC" and added a > MCELFStreamer.h to the same directory. That okay to do? This is not a trivial question, and I'll let others chip in. Superficially, you'd think so and it might make sense in the long run, but you have to consider why it wasn't there