Displaying 2 results from an estimated 2 matches for "gcc_o0".
Did you mean:
gcc_ok
2012 Apr 05
3
[LLVMdev] Implementing minimal debug info (-g1?) for Clang
.../codereview.appspot.com/4440072). This patch is used in Google for
about 2 years already.
I get the following binary sizes of 483.xalancbmk benchmark from SPEC 2006
(clang from trunk vs. gcc 4.6.x with Google patches):
11026073 Xalan_base.clang_O0
45882529 Xalan_base.clang_O0_g
11079688 Xalan_base.gcc_O0
16437776 Xalan_base.gcc_O0_gmlt
54221056 Xalan_base.gcc_O0_g
WDYT of implementing similar option in Clang? Clearly, there are two
options:
1. Don't modify Clang codegen, but instead erase all the extra debug info
by LLVM (pro - there actually is StripDebugInfo pass already, but it's very
s...
2012 Apr 09
0
[LLVMdev] Implementing minimal debug info (-g1?) for Clang
...440072). This patch is used in Google for about 2 years already.
>
> I get the following binary sizes of 483.xalancbmk benchmark from SPEC 2006 (clang from trunk vs. gcc 4.6.x with Google patches):
> 11026073 Xalan_base.clang_O0
> 45882529 Xalan_base.clang_O0_g
> 11079688 Xalan_base.gcc_O0
> 16437776 Xalan_base.gcc_O0_gmlt
> 54221056 Xalan_base.gcc_O0_g
>
> WDYT of implementing similar option in Clang? Clearly, there are two options:
> 1. Don't modify Clang codegen, but instead erase all the extra debug info by LLVM (pro - there actually is StripDebugInfo pass alr...