Hello, and other things

[Jason Fordham]

John,

Thanks for the JIT information!

The two things I need to come up with a design for now are how to get 
GCC to generate .class files, and what the runtime setup code needs to 
do. The former is a big task, because I need to have a fairly detailed 
design for the calling protocol. But that's all going to have to wait 
for later...

Jason

On 3/15/2008 11:20 AM, John Rose wrote:
> 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
>
> [1] http://mail.openjdk.java.net/pipermail/mlvm-dev/
> [2] http://openjdk.java.net/projects/mlvm/pdf/LangNet20080128.pdf
> ------------------------------------------------------------------------
>
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
>   

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~