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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ignition: V8 Interpreter

131 点作者 hittaruki将近 10 年前

11 条评论

hittaruki将近 10 年前
<a href="https:&#x2F;&#x2F;twitter.com&#x2F;andywingo&#x2F;status&#x2F;630705153922838528" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;andywingo&#x2F;status&#x2F;630705153922838528</a>
评论 #10034384 未加载
pwg将近 10 年前
See this: <a href="http:&#x2F;&#x2F;i.stanford.edu&#x2F;pub&#x2F;cstr&#x2F;reports&#x2F;cs&#x2F;tr&#x2F;94&#x2F;1520&#x2F;CS-TR-94-1520.pdf" rel="nofollow">http:&#x2F;&#x2F;i.stanford.edu&#x2F;pub&#x2F;cstr&#x2F;reports&#x2F;cs&#x2F;tr&#x2F;94&#x2F;1520&#x2F;CS-TR-9...</a> (ADAPTIVE OPTIMIZATION FOR SELF: RECONCILING HIGH PERFORMANCE WITH EXPLORATORY PROGRAMING)<p>Esp. section 5.3+ starting on physical pdf page 56.
评论 #10034410 未加载
s_kilk将近 10 年前
Can anyone summarize what this move will mean for performance on the average web app?<p>Will they be giving up some speed to claw back some memory?
评论 #10034332 未加载
评论 #10034401 未加载
twotwotwo将近 10 年前
This might be about RAM-constrained phones; the design doc refers to &#x27;--optimize-for-size devices&#x27;, suggesting it won&#x27;t (initially?) be on for everyone. Android and Chrome OS already enable Linux zram to get more out of low-memory gadgets. Incidentally, Google announced a (to me very ambitious-sounding) push for $50 Android phones today (<a href="http:&#x2F;&#x2F;www.engadget.com&#x2F;2015&#x2F;08&#x2F;10&#x2F;google-revamps-android-one-india&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.engadget.com&#x2F;2015&#x2F;08&#x2F;10&#x2F;google-revamps-android-on...</a>) that better low-RAM support could mesh nicely with, though of course it&#x27;s just a coincidence the dates lined up.
gsg将近 10 年前
Interesting decision.<p>The architecture sounds a little unusual:<p>&quot;The interpreter itself consists of a set of bytecode handler code snippets, each of which handles a specific bytecode and dispatches to the handler for the next bytecode. These bytecode handlers are written in a high level, machine architecture agnostic form of assembly code, as implemented by the RawMachineAssembler class and compiled by Turbofan&quot;<p>It also seems as if all calls are mediated by code generated by the compiler, which has the advantage of avoiding the awkwardness of different calling conventions between native and bytecode functions (possibly at some cost to performance?).<p>Fascinating reading. Thanks V8 people for allowing such documents to be public!
评论 #10035845 未加载
评论 #10036936 未加载
评论 #10036175 未加载
themckman将近 10 年前
I like the way Google projects seem to use Google Docs for this sort of thing. I&#x27;ve noticed in the past docs come up for projects like Angular and Go. I&#x27;d like to hear more about some of these documentation policies if anyone knows anything.
评论 #10035388 未加载
评论 #10035918 未加载
pietaalpha将近 10 年前
Would it be useful a &lt;hot-code&gt; tag for the purpose of indicating that optimizations are required for the code?<p>in Lisp we have compiler options (declare (optimize ...))
ilyaigpetrov将近 10 年前
Does this make implementation of other language compiled for V8 easier?
ndesaulniers将近 10 年前
So V8 will be moving from a two tier to a three tier architecture.<p>Spidermonkey is three tier and JSC is four.
评论 #10036085 未加载
评论 #10038432 未加载
felixangell将近 10 年前
The link to optimizing an ANSI C interpreter is broken, it&#x27;s missing a colon after the protocol. I dunno if there&#x27;s anyone here that can fix that, just thought I&#x27;d say it anyway.<p>Actually it&#x27;s not the colon, there are two protocols:<p><pre><code> http:&#x2F;&#x2F;http:&#x2F;&#x2F;dl.acm.org&#x2F;citation.cfm?id=199526 ^^^^^^^ </code></pre> My bad.
rancur将近 10 年前
by my deeds I will honor him, V8
评论 #10036965 未加载