Displaying 12 results from an estimated 12 matches for "gcc_except_table0".
Did you mean:
gcc_except_table
2011 Jul 28
0
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
...Z3barv:
LFB2:
pushq %rbp
LCFI0:
movq %rsp, %rbp
LCFI1:
pushq %rbx
LCFI2:
subq $40, %rsp
LCFI3:
leaq -17(%rbp), %rdi
call __ZN3BobC1Ev
leaq -18(%rbp), %rdi
call __ZN3BobC1Ev
leaq -19(%rbp), %rdi
call __ZN3BobC1Ev
LEHB0:
call __Z3foov
LEHE0:
<snip>
.section __TEXT,__gcc_except_tab
GCC_except_table0:
LLSDA2:
.byte 0xff
.byte 0xff
.byte 0x3
.byte 0x1a
.set L$set$0,LEHB0-LFB2 # from
.long L$set$0
.set L$set$1,LEHE0-LEHB0
.long L$set$1
.set L$set$2,L6-LFB2
.long L$set$2
.byte 0x0
i.e. the range of instructions covering the call to foo() has an action table
index of 0, meaning a cle...
2011 Jul 28
2
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
John,
I'm still not sure what you're talking about, I have
included the assembly
output from two compilations, one with a user explicit catch-all, one
with only an
implicit cleanup, the DWARF Action Table and Types Table are
absolutely identical,
as are the indexes used to reference the Action Table from the region
maps.
-Peter Lawrence.
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...trying to port my patches to latest llvm (svn
build) lately but i have one problem as far as the Exception Handling
mechanism is concerned. It seems that there are no Exception Tables
generated any more such as the one below:
.section .gcc_except_table,"a", at progbits
.align 4
GCC_except_table0:
.Lexception0:
.byte 255 # @LPStart Encoding = omit
.byte 3 # @TType Encoding = udata4
.uleb128 41 # @TType base offset
.byte 3 # Call site Encoding = udata4
.uleb128 39 # Ca...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
...nerated any more such
> as the one below:
got some example bitcode for which you see this (or, rather, don't see this
since the problem is that you are not seeing exception tables)?
Ciao, Duncan.
>
> .section .gcc_except_table,"a", at progbits
> .align 4
> GCC_except_table0:
> .Lexception0:
> .byte 255 # @LPStart Encoding = omit
> .byte 3 # @TType Encoding = udata4
> .uleb128 41 # @TType base offset
> .byte 3 # Call site Encoding = udata4
>...
2014 May 11
2
[LLVMdev] [cfe-dev] Code generation for noexcept functions
...mp5:
> movq %rax, %rdi
> callq __clang_call_terminate
> .Ltmp8:
> .size _Z5test2PFvvE, .Ltmp8-_Z5test2PFvvE
> .cfi_endproc
> .Leh_func_end0:
> .section .gcc_except_table,"a", at progbits
> .align 4
> GCC_except_table0:
> .Lexception0:
> .byte 255 # @LPStart Encoding = omit
> .byte 3 # @TType Encoding = udata4
> .asciz "\242\200\200" # @TType base offset
> .byte 3 # Call site En...
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...>
> got some example bitcode for which you see this (or, rather, don't see this
> since the problem is that you are not seeing exception tables)?
>
> Ciao, Duncan.
>
>>
>> .section .gcc_except_table,"a", at progbits
>> .align 4
>> GCC_except_table0:
>> .Lexception0:
>> .byte 255 # @LPStart Encoding = omit
>> .byte 3 # @TType Encoding = udata4
>> .uleb128 41 # @TType base offset
>> .byte 3 # Call site E...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
...example bitcode for which you see this (or, rather, don't see this
>> since the problem is that you are not seeing exception tables)?
>>
>> Ciao, Duncan.
>>
>>>
>>> .section .gcc_except_table,"a", at progbits
>>> .align 4
>>> GCC_except_table0:
>>> .Lexception0:
>>> .byte 255 # @LPStart Encoding = omit
>>> .byte 3 # @TType Encoding = udata4
>>> .uleb128 41 # @TType base offset
>>> .byte 3 # Call site Encoding = udata4
>>> .uleb128 39 # Call site table length
>>> .Lset0 = .Leh...
2011 Aug 05
0
[LLVMdev] RFC: Exception Handling Rewrite
...void foo() throw (A) {
baz();
}
void bar() throw (B) {
try {
foo();
} catch (const char *s) {
printf("%s\n", s);
}
}
GCC outputs this:
[Irk:llvm] gcc-4.2 -S -o - -dA t.cpp -O3
.text
.align 4,0x90
.globl __Z3foov
__Z3foov:
. . .
LEHB0:
call __Z3bazv
LEHE0:
. . .
GCC_except_table0:
LLSDA8:
.byte 0xff # @LPStart format (omit)
.byte 0x9b # @TType format (indirect pcrel sdata4)
.byte 0x25 # uleb128 0x25; @TType base offset
.byte 0x3 # call-site format (udata4)
.byte 0x1a # uleb128 0x1a; Call-site table length
.set L$set$0,LEHB0-LFB8
.long L$set$0 # region 0 start
.set L...
2011 Aug 05
3
[LLVMdev] RFC: Exception Handling Rewrite
Bill,
ooops, yes, I described the meaning of "throw(A)" backwards,
but I still
think my example shows why you cannot merge LandingpadInst while
inlining because multiple filter-lists on a LandingpadInst don't make
sense.
Perhaps I'm reading your original spec wrong, perhaps I'm mis-reading
Duncan's emails, but I read them to mean that your syntax supports
2010 Dec 02
0
[LLVMdev] Alternative exception handling proposal
...BD1Ev
movslq %ebx,%rdx
jmp L7
. . .
L7:
# basic block 15
movl %edx, %ebx
leaq -17(%rbp), %rdi
call __ZN1AD1Ev
movslq %ebx,%rdx
jmp L19
. . .
L19:
# basic block 19
cmpq $3, %rdx
je L9
# basic block 20
cmpq $2, %rdx
jne L30
# basic block 21
jmp L39
. . .
L39: # The catch handler
. . .
GCC_except_table0:
LLSDA4:
. . .
.set L$set$6,LEHB2-LFB4
.long L$set$6 # region 2 start
.set L$set$7,LEHE2-LEHB2
.long L$set$7 # length
.set L$set$8,L24-LFB4
.long L$set$8 # landing pad
.byte 0x7 # uleb128 0x7; action
. . .
.byte 0x1 # Action record table
.byte 0x0
.byte 0x2
.byte 0x7d
.byte 0x3
.b...
2014 Apr 01
6
[LLVMdev] Proposal: Loads/stores with deterministic trap/unwind behavior
...:
# BB#1: # %try.cont
popq %rdx
retq
.LBB0_2: # %lpad
.Ltmp2:
movq %rax, %rdi
callq _Unwind_Resume
.Ltmp4:
.size _Z3barv, .Ltmp4-_Z3barv
.cfi_endproc
.Leh_func_end0:
.section .gcc_except_table,"a", at progbits
.align 4
GCC_except_table0:
.Lexception0:
.byte 255 # @LPStart Encoding = omit
.byte 3 # @TType Encoding = udata4
.asciz "\256\200\200" # @TType base offset
.byte 3 # Call site Encoding = udata4
.byte 26 # Call site t...
2010 Dec 02
3
[LLVMdev] Alternative exception handling proposal
Hi Bill,
> This is similar to my first proposal.
yup, I still consider your first proposal to have been basically sound.
But it also suffers from a major problem,
> which stopped that proposal dead in its tracks. Namely, you have information in
> one place which needs to be shared in two different, but possibly disjoint,
> places: the type, filters, and personality information. In