search for: zplr

...the guy to look into this (CC'd). > Yeah, I'm seeing this in 4.0 as well. It looks as if the personality function isn't being output into the .s file. So we get something along the lines of this: Leh_frame_common_begin1: .long 0x0 .byte 0x1 .asciz "zPLR" .byte 0x1 .byte 0x7c .byte 0x8 .byte 0x7 .byte 0x1b .long ___gxx_personality_v0-. .byte 0x10 .byte 0x10 .byte 0xc .byte 0x4 .byte 0x4 .byte 0x88 .byte 0x1 .align 2 Leh_frame_c...

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

...g .Leh_frame_common_end-.Leh_frame_common_begin # Length of Common Information Entry .Leh_frame_common_begin: .long 0 # CIE Identifier Tag .byte 1 # CIE Version .asciz "zPLR" # CIE Augmentation .uleb128 1 # CIE Code Alignment Factor .sleb128 -8 # CIE Data Alignment Factor .byte 16 # CIE Return Addr...

...f > Common Information Entry > .Leh_frame_common_begin: > .long 0 > # CIE Identifier > Tag > .byte 1 > # CIE Version > .asciz "zPLR" # CIE > Augmentation > .uleb128 1 # CIE Code > Alignment Factor > .sleb128 -8 # CIE Data > Alignment Factor > .byte 16 >...

Hi, I'm trying to get exception handling working in my compiler targetting LLVM. I've been working from the LLVM exception handling documentation (including http://llvm.org/docs/ExceptionHandling.html and http://wiki.llvm.org/HowTo:_Build_JIT_based_Exception_mechanism) and looking at g++-llvm's output. I've been trying to get a minimal test function to work, which simply invokes

...try >> .Leh_frame_common_begin: >> .long 0 >> # CIE >> Identifier Tag >> .byte 1 >> # CIE Version >> .asciz "zPLR" # CIE >> Augmentation >> .uleb128 1 # CIE Code >> Alignment Factor >> .sleb128 -8 # CIE Data >> Alignment Factor >> .b...

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

.../ EH Common Frame header > + MCE->allocateSpace(PointerSize, 0); > + unsigned char* FrameCommonBeginPtr = (unsigned char*)MCE- > >getCurrentPCValue(); > + MCE->emitInt32((int)0); > + MCE->emitByte(dwarf::DW_CIE_VERSION); > + MCE->emitString(Personality ? "zPLR" : "zR"); > + MCE->emitULEB128Bytes(1); > + MCE->emitSLEB128Bytes(stackGrowth); > + MCE->emitByte(RI->getDwarfRegNum(RI->getRARegister(), true)); > + > + if (Personality) { > + MCE->emitULEB128Bytes(7); > + > + if (needsIndirectEnco...

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:

...> + > + unsigned char* StartCommonPtr = CurBufferPtr; > + // EH Common Frame header > + allocateSpace(PointerSize, 0); > + unsigned char* FrameCommonBeginPtr = CurBufferPtr; > + EmitInt32((int)0); > + EmitInt8(dwarf::DW_CIE_VERSION); > + EmitString(Personality ? "zPLR" : "zR"); > + EmitULEB128Bytes(1); > + EmitSLEB128Bytes(stackGrowth); > + EmitInt8(RI->getDwarfRegNum(RI->getRARegister(), true)); > + > + if (Personality) { > + EmitULEB128Bytes(7); > + > + if (TM.getTargetAsmInfo()->getNeedsIndirectEncodin...

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