Displaying 2 results from an estimated 2 matches for "dealwitharg".
Did you mean:
dealwithargs
2009 Jul 17
2
[LLVMdev] regression: double spaced asm output for thumb-2
...fstd d11, [sp, #+24]
fstd d10, [sp, #+16]
fstd d9, [sp, #+8]
fstd d8, [sp]
sub sp, sp, #872
mov r4, r1
mov r5, r0
cmp r0, #2
ble LBB1_133 @ entry.bb2.i_crit_edge
LBB1_1: @ bb.i
ldr r0, [r4, #+8]
bl L_atoi$stub
LBB1_2: @ bb2.i
str r0, [sp, #+80]
cmp r5, #1
ble LBB1_134 @ bb2.i.dealwithargs.exit_crit_edge
LBB1_3: @ bb3.i
ldr r0, [r4, #+4]
bl L_atoi$stub
LBB1_4: @ dealwithargs.exit
mov r4, r0
str r4, [sp, #+64]
mov r0, #32
ldr r5, [sp, #+80]
mov r1, r5
bl L___divsi3$stub
str r0, [sp, #+72]
mov r0, #64
mov r1, r5
bl L___divsi3$stub
str r0, [sp, #+76]
ldr r0, LCPI1_30...
2003 Nov 01
0
[LLVMdev] Cute profiling toy for LLVM
...2/516 localize_local
10. 1/516 initialize_graph
11. 1/516 clear_nummiss
12. 1/516 localize
13. 1/516 fill_all_from_fields
14. 1/516 update_all_from_coeffs
15. 1/516 make_all_neighbors
16. 1/516 make_tables
17. 1/516 __main
18. 1/516 main
19. 1/516 dealwithargs
NOTE: 1 function was never executed!
I've implemented function and basicblock profiling, because they were
simple. We should be able to add the path profiling component with little
trouble. The number of blocks instrumented could be reduced significantly
by making use of control equivalent...