Displaying 3 results from an estimated 3 matches for "replaypc".
Did you mean:
replay
2010 Apr 19
5
[LLVMdev] Code Size Benchmark
Hi all,
We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang
performed second in the test. The benchmark is CSiBE. Clang can't compile
the linux kernel (some inline asm not supported) and replaypc (error: use of
unknown builtin '__builtin_next_arg'). The concrete results are attached.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100419/32f3e0f4/attachment.html>
-------------- next part --...
2010 Apr 19
0
[LLVMdev] Code Size Benchmark
...:11 AM, Zhongxing Xu <xuzhongxing at gmail.com> wrote:
> Hi all,
>
> We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang
> performed second in the test. The benchmark is CSiBE. Clang can't compile
> the linux kernel (some inline asm not supported) and replaypc (error: use of
> unknown builtin '__builtin_next_arg'). The concrete results are attached.
That error looks extremely strange; where is the call to
__builtin_next_arg coming from?
-Eli
2010 Apr 19
0
[LLVMdev] Code Size Benchmark
On Apr 19, 2010, at 3:11 AM, Zhongxing Xu wrote:
> Hi all,
>
> We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang performed second in the test. The benchmark is CSiBE. Clang can't compile the linux kernel (some inline asm not supported) and replaypc (error: use of unknown builtin '__builtin_next_arg'). The concrete results are attached.
Nice, I don't have access to CSiBE. Out of curiosity, why aren't llvm -O2 numbers included? Would you be willing to track down a few examples of things where llvm is generating bigger code an...