Displaying 3 results from an estimated 3 matches for "llc_o0".
Did you mean:
llc_
2010 May 18
3
[LLVMdev] selection dag speedups / llc speedups
...amp;)
+ 13
16 llc.hg 0x00000000004d3112 main + 2802
17 libc.so.6 0x00007fb1725be1c4 __libc_start_main + 244
18 llc.hg 0x00000000004d0b09
Stack dump:
0. Program arguments: llc.hg -asm-verbose=false -O0
32/403.gcc/403.gcc.linked.bc -o
32/403.gcc/output/403.gcc.linked.bc.llc_O0.s
1. Running pass 'Function Pass Manager' on module
'32/403.gcc/403.gcc.linked.bc'.
2. Running pass 'Live Interval Analysis' on function
'@nonlocal_mentioned_p'
- Jan
On Mon, May 17, 2010 at 9:33 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote:...
2010 May 18
0
[LLVMdev] selection dag speedups / llc speedups
On May 17, 2010, at 9:09 PM, Rafael Espindola wrote:
>> The fast and local register allocators are meant to be used on unoptimized code, a 'Debug build'. While they do work on optimized code, they do not give good results. Their primary goal is compile time, not code quality.
>
> Yes, we have a somewhat uncommon use case. It is fine to spend time
> optimizing bitcode (LTO
2010 May 18
2
[LLVMdev] selection dag speedups / llc speedups
> The fast and local register allocators are meant to be used on unoptimized code, a 'Debug build'. While they do work on optimized code, they do not give good results. Their primary goal is compile time, not code quality.
Yes, we have a somewhat uncommon use case. It is fine to spend time
optimizing bitcode (LTO is a OK), but we want to make the final IL ->
Executable translation