Displaying 2 results from an estimated 2 matches for "6f63e637".
2010 Oct 09
0
[LLVMdev] LTO, plugins and binary sizes
...ng by the fix to 8313.
attached now.
Cheers,
--
Rafael Ávila de Espíndola
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm.patch
Type: text/x-patch
Size: 25795 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101009/6f63e637/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clang.patch
Type: text/x-patch
Size: 8168 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101009/6f63e637/attachment-0001.bin>
2010 Oct 09
4
[LLVMdev] LTO, plugins and binary sizes
For some time now I was curious on what the size impact of LTO was. I
decided to test this with a large C++ app, clang was a natural choice.
With PR8313 fixed with the proposed patch and PR8300 avoided by
disabling constructor aliasing I was able to hack clang to bootstrap
with LTO enabled using the gold plugin.
I did the testing on linux x86-64. Gcc is the 4.4.4 included with
Fedora 13. The