Displaying 3 results from an estimated 3 matches for "_mergedglobals".
Did you mean:
l_mergedglobals
2014 Mar 14
2
[LLVMdev] [ARM] [PIC] optimizing the loading of hidden global variable
Hi Rafael,
Yes, merging gv prevents linker to do garbage collection. Should it be implemented as a peephole pass? If we do it too early, the distance between GVs are not fixed yet.
PS:
Below is the GCC output with "extern" hidden:
ldr r2, .L2
stmfd sp!, {r3, lr}
.save {r3, lr}
.LPIC0:
add r0, pc, r2
bl _Z4initPv(PLT)
ldr r1, .L2+4
.LPIC1:
add r0, pc, r1
bl _Z4initPv(PLT)
ldr
2015 Apr 14
5
[LLVMdev] [cfe-dev] A problem with names that can not be demangled.
.... For
>
> example, take test/CodeGen/ARM/global-merge-addrspace.ll
>
>
>
> ; RUN: llc < %s -mtriple=thumb-apple-darwin -O3 | FileCheck %s
>
> ; Test the GlobalMerge pass. Check that the pass does not crash when using
>
> ; multiple address spaces.
>
> ; CHECK: _MergedGlobals:
>
> @g1 = internal addrspace(1) global i32 1
>
> @g2 = internal addrspace(1) global i32 2
>
> ; CHECK: _MergedGlobals1:
>
> @g3 = internal addrspace(2) global i32 3
>
> @g4 = internal addrspace(2) global i32 4
>
>
>
> With my change, the symbol is named Me...
2015 Apr 14
0
[LLVMdev] [cfe-dev] A problem with names that can not be demangled.
...ill always be correct, but the tests as written do not pass. For
example, take test/CodeGen/ARM/global-merge-addrspace.ll
; RUN: llc < %s -mtriple=thumb-apple-darwin -O3 | FileCheck %s
; Test the GlobalMerge pass. Check that the pass does not crash when using
; multiple address spaces.
; CHECK: _MergedGlobals:
@g1 = internal addrspace(1) global i32 1
@g2 = internal addrspace(1) global i32 2
; CHECK: _MergedGlobals1:
@g3 = internal addrspace(2) global i32 3
@g4 = internal addrspace(2) global i32 4
With my change, the symbol is named MergedGlobals.1, hence it fails this test.
I could change these 60 tes...