By: Exophase (exophase.delete@this.gmail.com), April 21, 2015 2:47 pm
Room: Moderated Discussions
RichardC (tich.delete@this.pobox.com) on April 21, 2015 12:57 pm wrote:
> but the Mill looks like a terrible architecture to
> run a branchy JVM
There's different types of branchy, and the JITs tend to load up on branches that are rarely taken. These types of branches could potentially be weathered decently by the Mill. Not quite the same thing, but Denver is wide and in-order and does a good job with Javascript code on Android, at least outside of the pathetic few millisecond runs of Sunspider. Part of that proficiency is probably due to its ability to very cheaply deal with branches that are deemed rarely taken.
Now if we're talking taken branches every few instructions then yeah, Mill could be in for some hurt.
> but the Mill looks like a terrible architecture to
> run a branchy JVM
There's different types of branchy, and the JITs tend to load up on branches that are rarely taken. These types of branches could potentially be weathered decently by the Mill. Not quite the same thing, but Denver is wide and in-order and does a good job with Javascript code on Android, at least outside of the pathetic few millisecond runs of Sunspider. Part of that proficiency is probably due to its ability to very cheaply deal with branches that are deemed rarely taken.
Now if we're talking taken branches every few instructions then yeah, Mill could be in for some hurt.