search for: ltmp7

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:

...f .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 member of Code Aurora Fo...

...is the output of ToT clang on this code: __Z3barv: ## @_Z3barv Ltmp5: .cfi_startproc .cfi_personality 155, ___gxx_personality_v0 Leh_func_begin0: .cfi_lsda 16, Lexception0 ## BB#0: ## %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 .a...

...# @_Z5test2PFvvE > .cfi_startproc > .cfi_personality 3, __gxx_personality_v0 > .Leh_func_begin0: > .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: # %_Z4testPFvv...

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.

Hi, I am trying to execute a simple hello world program compiled like so: path/to/compiled/clang -o test --target=aarch64-linux-gnu -march=armv8.5-a -fsanitize=hwaddress --sysroot=/usr/aarch64-linux-gnu/ -L/usr/lib/gcc/aarch64-linux-gnu/10.1.0/ -g test.c However, when I look at the disassembly, there is an unknown instruction listed at 0x2d51c: 000000000002d4c0 main: 2d4c0: ff c3 00 d1

...erated assembly .globl Main__TestProb .align 16, 0x90 .type Main__TestProb, at function Main__TestProb: # @Main__TestProb .cfi_startproc # BB#0: # %entry pushq %rbp .Ltmp5: .cfi_def_cfa_offset 16 .Ltmp6: .cfi_offset %rbp, -16 movq %rsp, %rbp .Ltmp7: .cfi_def_cfa_register %rbp subq $16, %rsp movq $0, -16(%rbp) movq $1, -8(%rbp) .align 16, 0x90 .LBB8_1: # %label_1 # =>This Inner Loop Header: Depth=1 movq -8(%rbp), %rcx movq %rsp, %rax addq $-16, %rax movq %rax, %rsp testq...

...', float 0.000000e+00, float 0.000000e+00, float 0.000000e+00, float 0.000000e+00> On a sandy bridge system, I've got similar behavior with a slightly different code (using AVX): pushl %ebp .Ltmp5: .cfi_def_cfa_offset 8 .Ltmp6: .cfi_offset %ebp, -8 movl %esp, %ebp .Ltmp7: .cfi_def_cfa_register %ebp movl 12(%ebp), %eax .loc 1 9 0 prologue_end # shufxbug.cl:9:0 .Ltmp8: vpermilps $65, 304(%eax), %xmm0 # xmm0 = mem[1,0,0,1] vxorps %xmm1, %xmm1, %xmm1 vinsertf128 $1, %xmm1, %ymm0, %ymm0 movl 16(%ebp), %eax .loc 1 10 0...

....type test, at function test: # @test .Ltmp4: .cfi_startproc # BB#0: # %entry pushq %rbp .Ltmp5: .cfi_def_cfa_offset 16 pushq %r14 .Ltmp6: .cfi_def_cfa_offset 24 pushq %rbx .Ltmp7: .cfi_def_cfa_offset 32 .Ltmp8: .cfi_offset %rbx, -32 .Ltmp9: .cfi_offset %r14, -24 .Ltmp10: .cfi_offset %rbp, -16 movl %edx, %ebx movq %rsi, %r14 movl %edi, %ebp cmpl $2, 4(%r14) jb .LBB0_2 .LBB0_2:...

...function moo: # @moo .Ltmp3: .cfi_startproc .Lfunc_begin0: .loc 1 12 0 # a.c:12:0 # BB#0: pushl %ebp .Ltmp4: .cfi_def_cfa_offset 8 .Ltmp5: .cfi_offset %ebp, -8 movl %esp, %ebp .Ltmp6: .cfi_def_cfa_register %ebp pushl %ebx subl $20, %esp .Ltmp7: .cfi_offset %ebx, -12 calll .L0$pb .L0$pb: popl %eax .Ltmp8: addl $_GLOBAL_OFFSET_TABLE_+(.Ltmp8-.L0$pb), %eax movl 8(%ebp), %ecx leal .L.str at GOTOFF(%eax), %edx movl %ecx, -8(%ebp) .loc 1 13 2 prologue_end # a.c:13:2 .Ltmp9: movl -8(%ebp), %ecx movl %edx, (%esp) movl %ecx, 4(%esp...

On Tue, Oct 18, 2011 at 6:58 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On Oct 18, 2011, at 5:22 PM, Chandler Carruth wrote: > > As for why it should be an IR pass, mostly because once the selection dag >> runs through the code, we can never recover all of the freedom we have at >> the IR level. To start with, splicing MBBs around requires known about