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 -------------- A non-text attachment was scrubbed... Name: result-size.png Type: image/png Size: 20482 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100419/32f3e0f4/attachment.png>
HMM, GCC is always the best. ---- email to: gjk.liu at gmail.com On Mon, Apr 19, 2010 at 6:11 PM, 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. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100419/14b324e3/attachment.html>
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 and file PRs? -Chris
On Mon, Apr 19, 2010 at 3: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
On Tue, Apr 20, 2010 at 2:15 AM, Chris Lattner <clattner at apple.com> wrote:> > 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 and file PRs? > >That was just a casual test when I was playing with LLVM. So I only tried the default configuration of CSiBE, which is -Os. I'll track down a few examples when I am free. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100420/4f865071/attachment.html>
On Tue, Apr 20, 2010 at 4:49 AM, Eli Friedman <eli.friedman at gmail.com>wrote:> On Mon, Apr 19, 2010 at 3: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? >The replaypc package of CSiBE (http://www.inf.u-szeged.hu/*csibe*/) only contains .i files. They were probably generated by gcc. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100420/d153626b/attachment.html>