Displaying 20 results from an estimated 62 matches for "ltmp1".
Did you mean:
tmp1
2011 Jul 28
2
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
..._attribute__((nothrow));
void bar ()
{
try {
foo();
} catch (...) {
print("caught (...)\n");
}
}
.section __TEXT,__gcc_except_tab
...
;; CallSite Table
.long Ltmp0-Leh_func_begin0
.long Ltmp1-Ltmp0 <--- this region
covers the call to foo
.long Ltmp2-Leh_func_begin0
.byte 1 <--- this is it's
Action Table index
...
;; Action Table
.byte 1
.byte 0
;; Types Table
.l...
2011 Jul 28
0
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
...## %entry
pushq %rbp
Ltmp6:
.cfi_def_cfa_offset 16
Ltmp7:
.cfi_offset %rbp, -16
movq %rsp, %rbp
Ltmp8:
.cfi_def_cfa_register %rbp
subq $80, %rsp
leaq -8(%rbp), %rdi
callq __ZN3BobC1Ev
leaq -16(%rbp), %rdi
callq __ZN3BobC1Ev
leaq -24(%rbp), %rdi
callq __ZN3BobC1Ev
Ltmp0:
callq __Z3foov
Ltmp1:
<snip>
.section __TEXT,__gcc_except_tab
.align 2
GCC_except_table0:
Lexception0:
.byte 255 ## @LPStart Encoding = omit
.byte 155 ## @TType Encoding = indirect pcrel sdata4
.byte 156 ## @TType base offset
.space 1
.byte 3...
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...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
.long .Lset2
.Lset3 = .Ltmp1-.Ltmp0 # Region length
.long .Lset3
.Lset4 = .Ltmp2-.Leh_func_begin0 # Landing pad
.long .Lset4
.uleb128 0 # Action
.Lset5 = .Ltmp1-.Leh_func_begin0 # Region start
.long .Lset5
.Lset6 = .Leh_func_end0-.Ltmp1 # Region...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
....Lset0
> .Lset1 = .Ltmp0-.Leh_func_begin0 # Region length
> .long .Lset1
> .long 0 # Landing pad
> .uleb128 0 # Action
> .Lset2 = .Ltmp0-.Leh_func_begin0 # Region start
> .long .Lset2
> .Lset3 = .Ltmp1-.Ltmp0 # Region length
> .long .Lset3
> .Lset4 = .Ltmp2-.Leh_func_begin0 # Landing pad
> .long .Lset4
> .uleb128 0 # Action
> .Lset5 = .Ltmp1-.Leh_func_begin0 # Region start
> .long .Lset5
> .Lset6 = ....
2014 May 11
2
[LLVMdev] [cfe-dev] Code generation for noexcept functions
...gin0:
> .cfi_lsda 3, .Lexception0
> # BB#0: # %entry
> pushq %rbx
> .Ltmp6:
> .cfi_def_cfa_offset 16
> .Ltmp7:
> .cfi_offset %rbx, -16
> movq %rdi, %rbx
> .Ltmp0:
> callq *%rbx
> .Ltmp1:
> # BB#1: # %_Z4testPFvvE.exit
> .Ltmp3:
> callq *%rbx
> .Ltmp4:
> # BB#2: # %_Z4testPFvvE.exit3
> popq %rbx
> retq
> .LBB0_3: # %terminate.lpad.i
>...
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...-.Leh_func_begin0 # Region length
>> .long .Lset1
>> .long 0 # Landing pad
>> .uleb128 0 # Action
>> .Lset2 = .Ltmp0-.Leh_func_begin0 # Region start
>> .long .Lset2
>> .Lset3 = .Ltmp1-.Ltmp0 # Region length
>> .long .Lset3
>> .Lset4 = .Ltmp2-.Leh_func_begin0 # Landing pad
>> .long .Lset4
>> .uleb128 0 # Action
>> .Lset5 = .Ltmp1-.Leh_func_begin0 # Region start
>> .lo...
2014 Feb 20
3
[LLVMdev] [LLVM] Forward temp label references on ARM in LDR with .ltorg in inline assembly are broken in trunk
...---
.file "lolwut.bc"
.text
.globl lolwut
.align 2
.type lolwut,%function
lolwut: @ @lolwut
.fnstart
@ BB#0: @ %entry
@APP
ldr r1, .Ltmp0
.align 2
.Ltmp0:
.long ".L11"
".L11":
@NO_APP
bx lr
.Ltmp1:
.size lolwut, .Ltmp1-lolwut
------------------------------------------
Somehow, the forward referenced label at 1: in the original assembly is getting mangled when its constant pool entry is created (the bad character is a 0x02 hex). In previous versions, the inline assembly was unchanged in...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
...n 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
>>> .long .Lset2
>>> .Lset3 = .Ltmp1-.Ltmp0 # Region length
>>> .long .Lset3
>>> .Lset4 = .Ltmp2-.Leh_func_begin0 # Landing pad
>>> .long .Lset4
>>> .uleb128 0 # Action
>>> .Lset5 = .Ltmp1-.Leh_func_begin0 # Region start
>>> .long .Lset5
>>> .Lset6 = .Leh_func_end0-.Ltmp1...
2014 Sep 02
3
[LLVMdev] LICM promoting memory to scalar
...<==== store inside loop
.LBB0_4: // %for.inc
// in Loop: Header=BB0_2 Depth=1
add w8, w8, w1
cmp w8, w0
b.lo .LBB0_2
.LBB0_5: // %for.end
ret
.Ltmp1:
.size _Z3fooii, .Ltmp1-_Z3fooii
.ident "clang version 3.6.0 "
Thanks,
Balaram
2014 Jan 18
2
[LLVMdev] Scheduling quirks
...gn 16, 0x90
.type _Z14test_scheduleri, at function
_Z14test_scheduleri: # @_Z14test_scheduleri
.cfi_startproc
# BB#0: # %entry
movl %edi, %eax
shrl $2, %eax
andl $15, %eax
shrl $3, %edi
andl $31, %edi
xorl %eax, %edi
movl %edi, %eax
retq
.Ltmp1:
.size _Z14test_scheduleri, .Ltmp1-_Z14test_scheduleri
.cfi_endproc
.ident "clang version 3.5 (trunk 199507)"
.section ".note.GNU-stack","", at progbits
<===
Now once more in detail.
The lines
x ^= (x >> 2);
and
x = x ^ (x >> 4);
and (!)...
2014 Sep 02
2
[LLVMdev] LICM promoting memory to scalar
...// %for.inc
>> // in Loop: Header=BB0_2 Depth=1
>> add w8, w8, w1
>> cmp w8, w0
>> b.lo .LBB0_2
>> .LBB0_5: // %for.end
>> ret
>> .Ltmp1:
>> .size _Z3fooii, .Ltmp1-_Z3fooii
>>
>>
>> .ident "clang version 3.6.0 "
>>
>> Thanks,
>> Balaram
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> L...
2020 Feb 28
2
Is BlockAddress always correct ?
Hi
I use BlockAddress to get the address of BasicBlock ,
and I use GlobalVariable 's getInitializer()
to pass the address of BasicBlock to the global variable of my own program
and then I print it out.
But , I found that BlockAddress is not always correct.
For example, some function's rsp (stack pointer) or other register is
maintained by caller,
so it would be like:
2014 Mar 26
3
[LLVMdev] [cfe-dev] computing a conservatively rounded square of a double
...leton_sqrd
> .align 16, 0x90
> .type _Z21inspect_singleton_sqrd, at function
> _Z21inspect_singleton_sqrd: # @_Z21inspect_singleton_sqrd
> .cfi_startproc
> # BB#0:
> vmulsd %xmm0, %xmm0, %xmm1
> vxorpd .LCPI1_0(%rip), %xmm1, %xmm0
> ret
> .Ltmp1:
> .size _Z21inspect_singleton_sqrd, .Ltmp1-_Z21inspect_singleton_sqrd
> .cfi_endproc
>
> I realize this is unsupported behavior, but it would be nice to still
> be able to use clang to do numerical computation. Is there a way to
> convince clang to not pull the multiplicat...
2011 Oct 17
0
[LLVMdev] LLVM Build Bot failure on llmv-x86_64-ubuntu
...l __unnamed_2+4(%rip), %eax
movd %eax, %xmm1
punpckldq %xmm2, %xmm1 # xmm1 = xmm1[0],xmm2[0],xmm1[1],xmm2[1]
punpckldq %xmm1, %xmm0 # xmm0 = xmm0[0],xmm1[0],xmm0[1],xmm1[1]
movd __unnamed_3(%rip), %xmm1
movss %xmm1, %xmm0
pshufb .LCPI0_0(%rip), %xmm0
movq %xmm0, __unnamed_2(%rip)
ret
.Ltmp1:
.size __unnamed_1, .Ltmp1-__unnamed_1
.Ltmp2:
.cfi_endproc
.Leh_func_end0:
.section ".note.GNU-stack","", at progbits
Odd?
Joe Abbey
Software Architect
Arxan Technologies, Inc.
1305 Cumberland Ave, Ste 215
West Lafayette, IN 47906
W: 765-889-4756 x2
C: 765-464-9893
jabb...
2013 Aug 01
0
[LLVMdev] Case sensitive .macros for llvm-mc and arithmetic in expressions
...;,\to
.endif
.endm
sum 0, 5
#---
Results in the following error:
sum.s:9:1: error: invalid operand for instruction
sum 0, 5
I have attached a patch that might be all that is needed to fix case
sensitivity.
In another case there is an expression like this:
#---
.Ltmp1:
.long 0xdeadbeef
.Ltmp7:
.long 0xdeadbeef
.Ltmp22:
.long (.Ltmp7-.Ltmp1) - .Ltmp22
#---
The above results in this error:
LLVM ERROR: expected relocatable expression
The above seems like it should work, and if .Ltmp22 is replaced by a
number it does.
--
Qualcomm Innovation Center, Inc. is a...
2014 Sep 03
3
[LLVMdev] LICM promoting memory to scalar
... <==== store
inside loop
.LBB0_4: // %for.inc
// in Loop: Header=BB0_2 Depth=1
add w8, w8, w1
cmp w8, w0
b.lo .LBB0_2
.LBB0_5: // %for.end
ret
.Ltmp1:
.size _Z3fooii, .Ltmp1-_Z3fooii
.ident "clang version 3.6.0 "
Thanks,
Balaram
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
___...
2012 Jan 24
0
[LLVMdev] Use of 'ldrd' instructions with unaligned addresses on armv7 (Major bug in LLVM optimizer?)
On Tue, Jan 24, 2012 at 08:36:17AM -0800, Esperanza de Escobar wrote:
> No one is arguing that there aren't ABI specs or LLVM design
> guidelines that say that unaligned accesses "should not", "could not"
> or "aren't guaranteed to" work, because it's besides the point.
No, it is the core of the issue. Standard C gives the compiler certain
2011 Jul 28
0
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
On Jul 28, 2011, at 8:41 AM, Peter Lawrence wrote:
> In short the problem is that there is an ambiguity between a cleanup handler having
> an Action Table entry that looks like
> .byte 1 ;; Type = 1 (ie #1 entry in Types Table)
> .byte 0 ;; Next = 0 (ie none, ie this is the list terminator for this try-statement)
> together with a corresponding Types Table entry #1 that looks
2014 Apr 01
6
[LLVMdev] Proposal: Loads/stores with deterministic trap/unwind behavior
...type _Z3barv, at function
_Z3barv: # @_Z3barv
.cfi_startproc
.cfi_personality 3, __gxx_personality_v0
.Leh_func_begin0:
.cfi_lsda 3, .Lexception0
# BB#0: # %entry
pushq %rax
.Ltmp3:
.cfi_def_cfa_offset 16
.Ltmp0:
movb (%rdi), %al
.Ltmp1:
# 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...
2013 Feb 28
2
[LLVMdev] Calling with register indirect reference instead of memory indirect reference.
...ct call with memory reference:
int main()
{
extern void (*foo)();
foo();
return 0;
}
And the corresponding assembly output is:
...
main: # @main
.cfi_startproc
# BB#0: # %entry
pushq %rax
.Ltmp1:
.cfi_def_cfa_offset 16
movl $2, %edi
callq *foo(%rip)
xorl %eax, %eax
popq %rdx
ret
...
The patch aims to make the memory reference to use a register reference by moving the address in...