This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bytecode verifier

From: Tom Tromey <tromey at redhat dot com>
To: Ranjit Mathew <rmathew at hotmail dot com>
Cc: java at gcc dot gnu dot org
Date: 26 Mar 2004 11:08:14 -0700
Subject: Re: Bytecode verifier
References: <1079384474.1995.85.camel@localhost.localdomain><1079532074.29202.1033.camel@localhost.localdomain><87oeqv49qc.fsf@fleche.redhat.com><16472.41028.957290.280721@cuddles.cambridge.redhat.com><878yhz47lb.fsf@fleche.redhat.com> <406429F2.9090306@hotmail.com>
Reply-to: tromey at redhat dot com

>>>>> "Ranjit" == Ranjit Mathew <rmathew@hotmail.com> writes:

Ranjit> Can you please elaborate a bit more? I mean, wouldn't this
Ranjit> create licensing issues? The configury will also get
Ranjit> a little weird I guess.

Andrew already answered about licensing.

I haven't yet tackled the configury, but yes, it will get weird.
There was a thread about this last year on the gcc list.  Perhaps
we'll have to add another bootstrap stage, or only build gcj in the
second stage, or something like that.

As for how it is done, basically I changed the verifier so things like
"class" are abstract, then any place we need information about a class
we have a defined C API for returning what we need.  Then in gcc we
just implement all of this in terms of trees.

Tom

References:
- Bytecode verifier
  - From: Andrew Haley
- Re: Bytecode verifier
  - From: Tom Tromey
- Re: Bytecode verifier
  - From: Ranjit Mathew

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]