Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of davanum@gmail.com designates
 64.233.170.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PJDw7eT2lcOgXH8zAWnhLuNLpOyMus3QQEI1dlUhLlieDfy4ONFtk/Hgwsmyv0xNjwoE/BrXgvuD83SfwbjdfXEy3wzT9UtJ+soc3rV96uvXHpO1HaE/e3suMX5EGFKG25/kZvIDpWz1COpBrQ8o15+TfzGbJynhEoBBfdve7UU=
Message-ID: <19e0530f050531061255806b1f@mail.gmail.com>
Date: Tue, 31 May 2005 09:12:42 -0400
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: harmony-dev@incubator.apache.org
Subject: JCVM on windows? (Re: [arch] VM Candidate : JC @
 http://jcvm.sourceforge.net/)
In-Reply-To: <428B5224.5060100@dellroad.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4288F308.9000502@dellroad.org>
	 <DF38AE11-5CD7-490B-BE27-27B0519EE312@apache.org>
	 <428B5224.5060100@dellroad.org>

Archie,

Just found this thread on jcvm mailing list:
http://sourceforge.net/mailarchive/forum.php?thread_id=3D7007768&forum_id=
=3D41274

Can you please comment on effort to port JCVM to windows platforms?

thanks,
dims

On 5/18/05, Archie Cobbs <archie@dellroad.org> wrote:
> Geir Magnusson Jr. wrote:
> > For those that want meaningful subjects lines, here it is and for  thos=
e
> > that are waiting for an architecture discussion - here it is.
> >
> > Here's the first of the offered VMs.  (I've privately mailed Tom van
> > Dijck about mudGE so we can look at something else)
> >
> > I've downloaded and will begin playing with today.  Archie, can you
> > give a brief overview of structure?
> >
> > Can we get some discussion about this from those that know about  about
> > VM architecture?
>=20
> The structure of JC is reasonably straightforward, i.e., the bits
> that are obviously going to be dependent (e.g., heap allocation code
> and GC code) are dependent, but otherwise there shouldn't be more than
> the "usual" amount of cross-dependency between code modules.
>=20
> Any of the "little" bits such as classfile parsing and ZIP/JAR decoding
> should be very modular and easily transplanted.
>=20
> The online manual provides some useful info about the overall design.
>=20
> Cross-cutting design issues include, as you might expect:
>=20
> - Object layout & lockword bits layout
> - Type, field, & method meta-data structures
> - Thread meta-data
> - How exceptions are thrown & caught
> - Stack frame layout (in JC, it's the same as C), stack unwinding
>=20
> On the topic of writing the VM in Java: this makes a lot of sense and
> there's no reason it should inherently be slower. In fact, eliminating
> the "impedence mismatch" between VM internal code execution and Java
> code execution was also one of the goals of JC as well (as a result, e.g.=
,
> the native methods in JC (not including JNI) have zero overhead). And
> JC's code generator is written in Java, so a major portion of JC is
> written in Java too.
>=20
> -Archie
>=20
> _________________________________________________________________________=
_
> Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.co=
m
>=20


--=20
Davanum Srinivas - http://webservices.apache.org/~dims/