mlvm-dev Digest, Vol 4, Issue 2

[Bharath Ravi Kumar]

John,

Looks like the link to the hotspot compiler wiki is broken. I got a 404 -
http://wikis.sun.com/display/HotSpotInternals/Compiler

-Bharath

Date: Sat, 15 Mar 2008 11:20:14 -0700
> From: John Rose <John.Rose at Sun.COM>
> Subject: Re: Hello, and other things
> To: Patrick Wright <pdoubleya at gmail.com>
> Cc: mlvm-dev at openjdk.java.net
> Message-ID: <8AC5FDE2-74EE-4EE6-91A2-8A094CD1463B at sun.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks for the excellent references.
> Since this list is archived[1], they are now
> bookmarked for us.
>
> On Mar 15, 2008, at 2:20 AM, Patrick Wright wrote:
> > Sorry if this is off-topic for the list, seems related to Jason's
> > original question on the thread.
>
> It's on-topic because of the such work may
> expose pain points[2] in the JVM for compiler
> back ends in general.  E.g., a botched JIT
> optimization forcing back end complexity
> for a C compiler would probably count as
> a point point.  From a quick scan of your first
> reference, I don't see any yet.  They probably
> have a lot more work to do moving their
> backend output closer to the JVM.
> For example, most C pointers can probably
> be rendered as offsets plus a base of a
> Java objects or array.  This requires a
> big pointer analysis, plus oracular advice
> from the user, but I think it would pay off.
>
> For a low-level account of JIT optimizations,
> see (and as you make discoveries contribute to)
> this wiki:
>   http://wikis.sun.com/display/HotSpotInternals/PerformanceTechniques
>   http://wikis.sun.com/display/HotSpotInternals/
>
> Best wishes,
> -- John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20080317/3eb57d80/attachment.html