Alexey Varlamov wrote:
Good news: with patches for HARMONY-677, I was able to run 1.5 classes
on DRLVM + classlib built with target=1.5.
But, I had some fun with the default javac (tried Sun jdk1.5.0_06 and
jrockit-jdk1.5.0-windows-ia32), which outwits itself in optimizing
String
Good news: with patches for HARMONY-677, I was able to run 1.5 classes
on DRLVM + classlib built with target=1.5.
But, I had some fun with the default javac (tried Sun jdk1.5.0_06 and
jrockit-jdk1.5.0-windows-ia32), which outwits itself in optimizing
String concatenations.
At first I got puzzled
Andrey Chernyshev wrote:
On 6/23/06, Mark Hindess [EMAIL PROTECTED] wrote:
On 23 June 2006 at 17:10, Tim Ellison [EMAIL PROTECTED] wrote:
Rana Dasgupta wrote:
On 6/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Pavel Pervov wrote:
Geir,
What's the first thing we do?
Folks,
I'm back to work, glad to hear all of you :).
Looks like planning and technical directions already settled, I'm
right in time to go coding ;)
Seriously, Pavel Pervov made good observation: very basic v49 support
only includes accepting the version number + groking new LDC
semantics. For
Besides, verifier code should be updated to support Java 5 changes.
On 22/06/06, Rana Dasgupta [EMAIL PROTECTED] wrote:
Geir,
Not sure at what level of detail you are asking, but we need some
changes in the DRLVM class support code to handle the new
class format. These include the
Pavel Pervov wrote:
Geir,
What's the first thing we do?
I'd suggest switching the build to 1.5.
The rest will come shortly :)
Now that's a plan! :)
geir
Pavel Pervov.
Intel Middleware Products Division.
On 6/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
This sounds easy
I'd suggest switching the build to 1.5.
The rest will come shortly :)
Now that's a plan! :)
Yeah, indeed. :)
Seriously speaking, DRLVM is already allowed to load class files with
version 49. Certainly, some issues will be brought up while trying to run
DRLVM against class library compiled
On 6/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Pavel Pervov wrote:
Geir,
What's the first thing we do?
I'd suggest switching the build to 1.5.
The rest will come shortly :)
Now that's a plan! :)
Hi Geir,
Actually what Pavel says makes sense. Not sure what plan we need. We
Hello,
I can give a little bit more details regarding 1.5 support enabling
for DRL VM. As Rana already mentioned there are 8 new attributes
should be supported by VM. To be precise there are three common
attributes (Signature_attribute, RuntimeVisibleAnnotations_attribute,
Rana Dasgupta wrote:
On 6/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Pavel Pervov wrote:
Geir,
What's the first thing we do?
I'd suggest switching the build to 1.5.
The rest will come shortly :)
Now that's a plan! :)
Hi Geir,
Actually what Pavel says makes sense. Not
On 23 June 2006 at 17:10, Tim Ellison [EMAIL PROTECTED] wrote:
Rana Dasgupta wrote:
On 6/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Pavel Pervov wrote:
Geir,
What's the first thing we do?
I'd suggest switching the build to 1.5.
The rest will come shortly :)
Now
-Original Message-
From: Mark Hindess [mailto:[EMAIL PROTECTED]
My feeling at the moment is that although drlvm and classlib are working
together[0], it is evident[1] that things are not really integrated.
I would prefer to see real integration before we break[0] things by
moving
There are modest changes to the classfile format that need to be
supported; once they are in place we can remove the compiler-hack.
Regards,
Tim
Geir Magnusson Jr wrote:
It seems we're in general agreement that getting DRLVM to deal with Java
5 classfiles is a good place to start.
It
Geir,
Not sure at what level of detail you are asking, but we need some
changes in the DRLVM class support code to handle the new
class format. These include the acc_synthetic , acc_annotation etc. access
modifiers, the new attrs like enclosingClass, runtime
visible/invisible attrs,
This sounds easy and fun.
What's the first thing we do?
geir
Rana Dasgupta wrote:
Geir,
Not sure at what level of detail you are asking, but we need some
changes in the DRLVM class support code to handle the new
class format. These include the acc_synthetic , acc_annotation etc. access
It seems we're in general agreement that getting DRLVM to deal with Java
5 classfiles is a good place to start.
It supports our project desire to get off the target=jsr14 hack for
compiling.
So, for those that know the DRLVM codebase, what are the steps?
Anyone who throws the One Big Patch over
16 matches
Mail list logo
