[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JIT pluggability
From: |
C. Brian Jones |
Subject: |
Re: JIT pluggability |
Date: |
Fri, 09 Jan 2004 07:57:34 -0500 |
On Fri, 2004-01-09 at 03:45, Sascha Brawer wrote:
> Tom Tromey <address@hidden> wrote on Thu, 8 Jan 2004 17:48:59 -0700:
>
> >[standard pluggable JIT interface]
>
> This would indeed be quite nice, IMHO.
>
> >Language choice for API.
> > The obvious choices being:
> > C lowest common denominator
> > C++ next-to-lowest common denominator :-) provides some
> > abstraction benefit, maybe
> > Java using our own tools...
Going off on a tangent, are there other interfaces where reuse may be
possible such as JVMPI, JPDA, and the wire protocols for those... if the
hooks into the free JVMs are somewhat standard? Essentially Sun wrapped
the native interfaces like JVMPI with Java in JPDA which made the tasks
of writing profilers or debuggers somewhat easier. So these Java
wrappers should be the same if written to the C interfaces that
pre-existed JPDA but then all the JVMs need to support those
interfaces. To what extent should Classpath provide parts of the
debugging/profiling solution?
Thanks,
Brian
signature.asc
Description: This is a digitally signed message part
- JIT pluggability, Tom Tromey, 2004/01/08
- Re: JIT pluggability, Sascha Brawer, 2004/01/09
- Re: JIT pluggability (ABI Issues), Patrik Reali, 2004/01/12
- Re: JIT pluggability (ABI Issues), Chris Gray, 2004/01/13
- Re: JIT pluggability (ABI Issues), shudo, 2004/01/13
- Re: JIT pluggability (ABI Issues), Sascha Brawer, 2004/01/13