Re:Silver: A free implementation of Swift for .NET, Java, An...
by marcosscriven on Monday February 09, 2015 @05:45AM
(#9020538)
The point I was trying to get across is that by cross-compiling from C/C++ with Emscripten, static type information can be used to give native performance, that a program written directly in Javascript wouldn't. It's still AOT in that sense - it's not like JIT where only hot bits of code get converted to native to code, and only then when some heuristics have determined what actual types the code ends up dealing with at runtime.
[ Parent
| on HN ]
Re:Silver: A free implementation of Swift for .NET, Java, An...
by pjmlp on Monday February 09, 2015 @08:31AM
(#9021029)
But it isn't AOT in CS speak.
Re:Silver: A free implementation of Swift for .NET, Java, An...
by marcosscriven on Monday February 09, 2015 @09:23PM
(#9025028)
I'm not sure how you claim to be the authority on 'CS speak', but it's a sufficiently blurred line here, for reasons I clearly explained and which you seem unable to understand.
Emscripten/asm.js can use static information to generate Javascript which can be compiled to native code, before the code in question is run, aka Ahead of Time.
Re:Silver: A free implementation of Swift for .NET, Java, An...
by pjmlp on Tuesday February 10, 2015 @02:59AM
(#9025906)
Well, I majored in compiler design.
Ahead of time compilation is used to describe the process of generating machine code at compilation time, in a form that can be executed directly by a processor without any additional transformation process.
Which clearly is not happening here, as the code is converted into JavaScript and relies on a JavaScript implementation to run. Regardless of the optimization processes used by the JavaScript engine.
Re:Silver: A free implementation of Swift for .NET, Java, An...
by marcosscriven on Tuesday February 10, 2015 @07:16AM
(#9026684)
The nuances unfortunately appear to escape you.