Comments on: SquirrelFish

By: click

click — Thu, 13 Aug 2009 03:29:48 +0000

Thank you. You have helped someone more than you could know.

By: pocker

pocker — Mon, 15 Jun 2009 02:45:42 +0000

I really like the layout and colors that you chose for this website! It certainly is incredible!

By: Blaisorblade

Blaisorblade — Sun, 18 Jan 2009 02:30:32 +0000

@Rob Mueller: you’re quite right. Actually, the point of direct threading is not about skipping the range check. Actually, it’s a pity that the post doesn’t mention the branch prediction issue.

It’s the main issue discussed by the paper mentioned in Squirrelfish announce, The Structure and Performance of Eﬃcient Interpreters, by Anton Ertl (author of the benchmarks at http://www.complang.tuwien.ac.at/forth/threading/) and David Gregg.

By: Daniel Shorten » Chrome:

Daniel Shorten » Chrome: — Fri, 12 Sep 2008 17:35:25 +0000

[...] David Mandelin’s blog » SquirrelFish Details about a highly optimized JavaScript engine. [...]

By: Inline threading, TraceMonkey, etc. :: David Mandelin’s blog

Inline threading, TraceMonkey, etc. :: David Mandelin’s blog — Thu, 28 Aug 2008 02:57:11 +0000

[...] Basically, this is yet another interpreter opcode dispatch technique. I previously wrote about opcode dispatch, concluding that direct-threading, in which the opcode is a target address, and the code to start [...]

By: chad

chad — Tue, 17 Jun 2008 00:18:50 +0000

some non-technical trivia: There is a bootleg store in China called “Squirrel–shaped Fish”. In China it’s standard procedure for stores to illegally use names and logos from large international brands. With this store, they stole the Lacoste alligator logo, but made their own name. Pretty genius.

http://chadvonnau.com/china/4/15.IMG_4485_bootlegs.jpg

By: SD

SD — Fri, 13 Jun 2008 08:01:44 +0000

wonderer – The reason Mozilla are still developing their own JS engine is simple – Mozilla’s JS engine supports a lot of stuff that Safari’s does not. Type annotations, for example, or all kinds of other ECMAScript 3 and 4 features. The entire UI of Firefox is written using JavaScript, and it makes heavy use of all those features that would be missing with Safari’s JS engine.

By: Andreas

Andreas — Thu, 05 Jun 2008 15:35:25 +0000

Register-based bytecodes are not necessarily easier to compile, especially if you are trying to compile with a very fast and simple JIT. The stack semantics implicitly tells you when temporary values go dead (and the associated register can be de-allocated), wheres in case of registers you need proper liveness analysis.

By: Matthew

Matthew — Thu, 05 Jun 2008 00:08:59 +0000

Interesting stuff.

Might another advantage of the register-based approach be that it’s easier to map to register-based CPU architectures when JIT compiling bits of bytecode?

I dunno, I’m asking

By: Dave Mandelin of Mozilla explains Squirr … « Random Trap

Dave Mandelin of Mozilla explains Squirr … « Random Trap — Wed, 04 Jun 2008 17:16:46 +0000

[...] javascript Dave Mandelin of Mozilla explains Squirrelfish, WebKit’s new JS Interpreter: http://blog.mozilla.com/dmandelin/2008/06/03/squirrelfish/ [...]