IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Secondary stage.
Bytecode to native. I've been noticing that Sun's Windows Java implementation takes a VERY long time to start, and my guess is that they're compiling the whole program before running it - which would explain the long start time.

The way I'd really want it to work is a hybrid of the two: Allow flagging of specific components to be "pre-compiled" on launch, if you don't want any lag for those components, and let the rest be compiled on the fly. CLR doesn't allow for that - everything is compiled on the fly, as near as near as I can tell.
"He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you." - Friedrich Nietzsche
New Compiled as Needed
The bytecode to native code JITing happens on an as neede basis. That's why startup is so long ... every bit of code that you hit is fresh and could potentially be compiled.

From your description of C$/CLR, the only difference I see is that CLR will unconditionally compile to native code immediately. HotSpot does not necessarily compile everything, only the "hot spots".
--
-- Jim Weirich jweirich@one.net [link|http://w3.one.net/~jweirich|http://w3.one.net/~jweirich]
---------------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)
     Does Java do incremental compilation? - (inthane-chan) - (5)
         Two stages of compile... - (ChrisR) - (2)
             Secondary stage. - (inthane-chan) - (1)
                 Compiled as Needed - (JimWeirich)
         Good discussion paper - (Mike) - (1)
             Interesting. - (inthane-chan)

Sounds like a horse. Maybe it was.
33 ms