Displaying 12 results from an estimated 12 matches for "lset0".
2013 Sep 21
2
[LLVMdev] Debug info failing in assembler.
....L.debug_info_begin0 # Offset Into Debug Info Section
.byte 4 # Address Size (in bytes)
.byte 0 # Segment Size (in bytes)
.byte 255
.byte 255
.byte 255
.byte 255
.long comm
.Lset0 = .L.bss_end-comm
.long .Lset0
The typical error message is:
/tmp/debug-8ecf9d.s: Assembler messages:
/tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections)
for `-' when setting `.Lset0'
Is it legal to mix .comm symbols and .bss symbols in assembly? Is the
x86...
2013 Sep 21
0
[LLVMdev] Debug info failing in assembler.
...t Into Debug Info Section
> .byte 4 # Address Size (in bytes)
> .byte 0 # Segment Size (in bytes)
> .byte 255
> .byte 255
> .byte 255
> .byte 255
> .long comm
> .Lset0 = .L.bss_end-comm
> .long .Lset0
>
> The typical error message is:
> /tmp/debug-8ecf9d.s: Assembler messages:
> /tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections) for
> `-' when setting `.Lset0'
>
> Is it legal to mix .comm symbols and ....
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...yte 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_func_begin0-.Leh_func_begin0 # Region start
.long .Lset0
.Lset1 = .Ltmp0-.Leh_func_begin0 # Region length
.long .Lset1
.long 0 # Landing pad
.uleb128 0 # Action
.Lset2 = .Ltmp0-.Leh_func_begin0 # Region start
....
2013 Sep 22
1
[LLVMdev] Debug info failing in assembler.
...t Into Debug Info Section
> .byte 4 # Address Size (in bytes)
> .byte 0 # Segment Size (in bytes)
> .byte 255
> .byte 255
> .byte 255
> .byte 255
> .long comm
> .Lset0 = .L.bss_end-comm
> .long .Lset0
>
> The typical error message is:
> /tmp/debug-8ecf9d.s: Assembler messages:
> /tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections)
> for `-' when setting `.Lset0'
>
> Is it legal to mix .comm symbols and...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
...# @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_func_begin0-.Leh_func_begin0 # Region start
> .long .Lset0
> .Lset1 = .Ltmp0-.Leh_func_begin0 # Region length
> .long .Lset1
> .long 0 # Landing pad
> .uleb128 0 # Action
> .Lset2 = .Ltmp0-.Leh_func_...
2011 Jul 28
0
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
...## Call site table length
## >> Call Site 1 <<
## Call between Ltmp0 and Ltmp1
## jumps to Ltmp2
## On action: cleanup
Lset0 = Ltmp0-Leh_func_begin0
.long Lset0
Lset1 = Ltmp1-Ltmp0
.long Lset1
Lset2 = Ltmp2-Leh_func_begin0
.long Lset2
.byte 0
Same thing.
For contrast, here is the result from gcc-4.2 on your catch-all code:
.globl __Z3barv
__Z3barv:
LFB2:
pushq %rbp
LCFI0:
movq %rsp, %rbp
LCFI1:
LEHB0:
call __Z3...
2014 May 11
2
[LLVMdev] [cfe-dev] Code generation for noexcept functions
...> .byte 3 # @TType Encoding = udata4
> .asciz "\242\200\200" # @TType base offset
> .byte 3 # Call site Encoding = udata4
> .byte 26 # Call site table length
> .Lset0 = .Ltmp0-.Leh_func_begin0 # >> Call Site 1 <<
> .long .Lset0
> .Lset1 = .Ltmp1-.Ltmp0 # Call between .Ltmp0 and .Ltmp1
> .long .Lset1
> .Lset2 = .Ltmp2-.Leh_func_begin0 # jumps to .Ltmp2
> .long .Lset2
>...
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...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_func_begin0-.Leh_func_begin0 # Region start
>> .long .Lset0
>> .Lset1 = .Ltmp0-.Leh_func_begin0 # Region length
>> .long .Lset1
>> .long 0 # Landing pad
>> .uleb128 0 # Action
>>...
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
0
[LLVMdev] Exception Tables in latest LLVM
...xcept_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_func_begin0-.Leh_func_begin0 # Region start
>>> .long .Lset0
>>> .Lset1 = .Ltmp0-.Leh_func_begin0 # Region length
>>> .long .Lset1
>>> .long 0 # Landing pad
>>> .uleb128 0 # Action
>>> .Lset2 = .Ltmp0-.Leh_func_begin0 # Region start
>&...
2012 Mar 20
0
[LLVMdev] Runtime linker issue wtih X11R6 on i386 with -O3 optimization
...# DW_FORM_addr
.byte 64 # DW_AT_frame_base
.byte 10 # DW_FORM_block1
.byte 0 # EOM(1)
.byte 0 # EOM(2)
.byte 0 # EOM(3)
.Labbrev_end:
.section .debug_pubnames,"", at progbits
.Lset0 = .Lpubnames_end1-.Lpubnames_begin1 # Length of Public Names Info
.long .Lset0
.Lpubnames_begin1:
.short 2 # DWARF Version
.long .Linfo_begin1 # Offset of Compilation Unit Info
.Lset1 = .Linfo_end1-.Linfo_begin1 # Compilation Unit Length
.long .Lset1
.long...
2014 Apr 01
6
[LLVMdev] Proposal: Loads/stores with deterministic trap/unwind behavior
...0:
.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 table length
.Lset0 = .Ltmp0-.Leh_func_begin0 # >> Call Site 1 <<
.long .Lset0
.Lset1 = .Ltmp1-.Ltmp0 # Call between .Ltmp0 and .Ltmp1
.long .Lset1
.Lset2 = .Ltmp2-.Leh_func_begin0 # jumps to .Ltmp2
.long .Lset2
.byte 5 # On action: 3
.Lset3...