TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

V8 is faster than GCC

68 点作者 wingo将近 14 年前

9 条评论

cloudhead将近 14 年前
I can't even begin to explain how wrong this benchmark and the author's conclusion is. I'd rather see a benchmark of apache vs a fibonacci function than read this nonsense.
评论 #2642223 未加载
评论 #2642538 未加载
pcwalton将近 14 年前
This is a banal point. Yes, separate compilation hurts performance. But that's what link-time optimization is for. GCC and LLVM alike can both do link-time optimization.<p>You might as well say "gcc with -O0 is slower than V8, therefore V8 is faster than gcc".
评论 #2642741 未加载
PassTheAmmo将近 14 年前
How about trying a benchmark that mimics an actual program that someone would use.
strmpnk将近 14 年前
Obscure? It's interesting but I can't see a case where I'd be recompiling C code every time I want to run something. On the other hand, we can't just go AOT compile using V8 (AFAIK) so let's call V8 always slower?
评论 #2642337 未加载
hammerdr将近 14 年前
In my mind, the value of this benchmark isn't to prove that V8 is absolutely faster than C but that there is intrinsic value in doing runtime compilation instead of / on top of compile-time optimizations.<p>It's a demonstration of <i>why</i> run time optimizing compilers/runtimes may one day become faster than compile time optimizing compilers.
st3fan将近 14 年前
Yay! Another useless benchmark!
neuroelectronic将近 14 年前
No kidding.
d0vs将近 14 年前
What.
nickik将近 14 年前
Every reader of that blogpost: Oh blabla unfair, the C code of the thing would be faster if the thing had included the other thing blabla.<p>I think its a fun benchmark :)