search for: ltmp5

Displaying 20 results from an estimated 22 matches for "ltmp5".

Did you mean: tmp5
2013 Sep 20
2
[LLVMdev] LLVM ERROR: expected relocatable expression
This example generates the following error: .Ltmp3: .Ltmp5: .Ltmp13: .word (.Ltmp5-.Ltmp3)-.Ltmp13 ./llvm-mc ex.s -filetype=obj LLVM ERROR: expected relocatable expression when using: -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
2012 May 24
4
[LLVMdev] use AVX automatically if present
....cfi_def_cfa_offset 16 .Ltmp3: .cfi_offset %rbp, -16 movq %rsp, %rbp .Ltmp4: .cfi_def_cfa_register %rbp vmovaps (%rdi), %ymm0 vaddps (%rsi), %ymm0, %ymm0 vmovaps %ymm0, (%rdi) popq %rbp vzeroupper ret .Ltmp5: .size _fun1, .Ltmp5-_fun1 .cfi_endproc .section ".note.GNU-stack","", at progbits I guess your answer is that I did not specify a target triple. However why is SSE41 automatically detected and AVX is not?
2012 May 24
0
[LLVMdev] use AVX automatically if present
...p3: > .cfi_offset %rbp, -16 > movq %rsp, %rbp > .Ltmp4: > .cfi_def_cfa_register %rbp > vmovaps (%rdi), %ymm0 > vaddps (%rsi), %ymm0, %ymm0 > vmovaps %ymm0, (%rdi) > popq %rbp > vzeroupper > ret > .Ltmp5: > .size _fun1, .Ltmp5-_fun1 > .cfi_endproc > > > .section ".note.GNU-stack","", at progbits > > > > > I guess your answer is that I did not specify a target triple. However why is > SSE41 automatically detected and...
2013 Sep 20
0
[LLVMdev] LLVM ERROR: expected relocatable expression
On Fri, Sep 20, 2013 at 2:50 PM, Sid Manning <sidneym at codeaurora.org> wrote: > > This example generates the following error: > .Ltmp3: > .Ltmp5: > .Ltmp13: > .word (.Ltmp5-.Ltmp3)-.Ltmp13 > > ./llvm-mc ex.s -filetype=obj > LLVM ERROR: expected relocatable expression when using: > > Umm, isn't this equivalent to the following? What do you expect LLVM to do with it? .Ltmp13: .word -.Ltmp13 -Eli -----...
2013 Sep 22
2
[LLVMdev] LLVM ERROR: expected relocatable expression
On 09/20/2013 06:00 PM, Eli Friedman wrote: > On Fri, Sep 20, 2013 at 2:50 PM, Sid Manning <sidneym at codeaurora.org > <mailto:sidneym at codeaurora.org>> wrote: > > > This example generates the following error: > .Ltmp3: > .Ltmp5: > .Ltmp13: > .word (.Ltmp5-.Ltmp3)-.Ltmp13 > > ./llvm-mc ex.s -filetype=obj > LLVM ERROR: expected relocatable expression when using: > > > Umm, isn't this equivalent to the following? What do you expect LLVM to > do with it? > > .Lt...
2014 May 11
2
[LLVMdev] [cfe-dev] Code generation for noexcept functions
...# %_Z4testPFvvE.exit3 > popq %rbx > retq > .LBB0_3: # %terminate.lpad.i > .Ltmp2: > movq %rax, %rdi > callq __clang_call_terminate > .LBB0_4: # %terminate.lpad.i2 > .Ltmp5: > 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...
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:
2013 Sep 22
0
[LLVMdev] LLVM ERROR: expected relocatable expression
...20/2013 06:00 PM, Eli Friedman wrote: > >> On Fri, Sep 20, 2013 at 2:50 PM, Sid Manning <sidneym at codeaurora.org >> <mailto:sidneym at codeaurora.org**>> wrote: >> >> >> This example generates the following error: >> .Ltmp3: >> .Ltmp5: >> .Ltmp13: >> .word (.Ltmp5-.Ltmp3)-.Ltmp13 >> >> ./llvm-mc ex.s -filetype=obj >> LLVM ERROR: expected relocatable expression when using: >> >> >> Umm, isn't this equivalent to the following? What do you expect LLVM t...
2012 May 24
2
[LLVMdev] use AVX automatically if present
...movq %rsp, %rbp > > .Ltmp4: > > .cfi_def_cfa_register %rbp > > vmovaps (%rdi), %ymm0 > > vaddps (%rsi), %ymm0, %ymm0 > > vmovaps %ymm0, (%rdi) > > popq %rbp > > vzeroupper > > ret > > .Ltmp5: > > .size _fun1, .Ltmp5-_fun1 > > .cfi_endproc > > > > > > .section ".note.GNU-stack","", at progbits > > > > > > > > > > I guess your answer is that I did not specify a target triple. &gt...
2011 Jul 28
0
[LLVMdev] LLVMdev Digest, Vol 85, Issue 50
....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 cleanup. Here 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 l...
2014 Nov 06
2
[LLVMdev] Should the MachineVerifier accept a MBB with a single (landing pad) successor?
...B <BB#8> Successors according to CFG: BB#8(1) BB#9(1) BB#8: derived from LLVM BB %invoke.cont43 Predecessors according to CFG: BB#7 BB#9: derived from LLVM BB %lpad40, EH LANDING PAD Predecessors according to CFG: BB#7 EH_LABEL <MCSym=Ltmp5> ... The unreachable BB#8 gets removed, and we end up with: BB#5: derived from LLVM BB %invoke.cont41 ... B <BB#8> Successors according to CFG: BB#8(2) ... BB#8: derived from LLVM BB %lpad40, EH LANDING PAD Predecessors acc...
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.
2012 Feb 25
3
[LLVMdev] Missed optimization on array initialization
...tadata !"omnipotent char", metadata !2} !2 = metadata !{metadata !"Simple C/C++ TBAA",null} and this gets emitted as (for x64, but x86 is similar): # BB#0: pushq %rbx .Ltmp3: .cfi_def_cfa_offset 16 subq $400, %rsp # imm = 0x190 .Ltmp4: .cfi_def_cfa_offset 416 .Ltmp5: .cfi_offset %rbx, -16 movl %edi, %ebx leaq (%rsp), %rdi xorl %esi, %esi movl $400, %edx # imm = 0x190 callq memset movl %ebx, (%rsp) testl %ebx, %ebx jne .LBB0_2 # BB#1: leaq (%rsp), %rdi callq _Z3barPi .LBB0_2: addq $400, %rsp # imm = 0x190 popq %rbx ret I...
2017 Aug 21
3
DragonEgg for GCC v8.x and LLVM v6.x is just able to work
...bl main .p2align 4, 0x90 .type main, at function main: # @main .cfi_startproc # BB#0: # %entry pushq %rbp .Ltmp3: .cfi_def_cfa_offset 16 .Ltmp4: .cfi_offset %rbp, -16 movq %rsp, %rbp .Ltmp5: .cfi_def_cfa_register %rbp subq $32, %rsp movl %edi, -8(%rbp) movq %rsi, -16(%rbp) movl $.L.cst.3, %edi movl $.L.cst.2, %esi movl $1, %edx xorl %eax, %eax callq printf movl $0, -4(%rbp) movl -4(%rbp), %eax ad...
2012 Feb 28
0
[LLVMdev] inspecting value of formal parameter in gdb for x86
...ax .Ltmp2: #DEBUG_VALUE: foo:c <- ESP+4294967295 # argpass.c:5:14 movl 8(%ebp), %esi .loc 1 7 5 .Ltmp4: movl %esi, (%esp) # argpass.c:7:5 calll bar # argpass.c:7:5 testl %esi, %esi je .LBB0_2 # BB#1: .loc 1 10 1 .Ltmp5: addl $4, %esp # argpass.c:10:1 .Ltmp6: #DEBUG_VALUE: foo:c <- ESP+4294967295 popl %esi # argpass.c:10:1 popl %ebp # argpass.c:10:1 ret # argpass.c:10:1 ... 'c' parameter is in...
2015 Oct 27
3
segv inside loop on x86_64
...preds = %else_1 ret void } compiles ok with stock llc Here's the generated 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: Dept...
2011 May 17
1
[LLVMdev] [cfe-dev] x86_64-pc-win32 ABI var arg code gen bug? Is the bitcode correct? Or is it the code gen?
...is generated and there is a > bug in that chunk of code? > > clang -ccc-host-triple x86_64-pc-win32  -S  v.c > .globl ShellPrintHiiEx > .align 16, 0x90 > ShellPrintHiiEx:                        # @ShellPrintHiiEx > # BB#0: > pushq %rbp > .Ltmp4: > movq %rsp, %rbp > .Ltmp5: > subq $80, %rsp > .Ltmp6: > movq 48(%rbp), %rax > movl %ecx, -4(%rbp) > movl %edx, -8(%rbp) > movq %r8, -16(%rbp) > movq %r9, -24(%rbp) > movq %rax, -32(%rbp) > leaq 48(%rbp), %rax > movq %rax, -40(%rbp) > movq %rax, %rcx > callq ReturnMarker > movl %eax, -4...
2020 Jun 22
3
Hardware ASan Generating Unknown Instruction
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
2013 Feb 19
2
[LLVMdev] Is it a bug or am I missing something ?
...'elem_0_of_source' , float 'elem_0_of_source', float 'elem_1_of_source', 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, %x...
2011 Oct 19
0
[LLVMdev] Question regarding basic-block placement optimization
...-o - ifchain.ll .file "ifchain.ll" .text .globl test .align 16, 0x90 .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...