I created an MMTk page off the DRLVM core VM development page and put in
Weldon's list.
On 10/23/06, Gregory Shimansky [EMAIL PROTECTED] wrote:
Weldon, can you make a subpage to Rana's list and link it to the MMTK
integration item?
On 10/31/06, Rana Dasgupta [EMAIL PROTECTED] wrote:
I created an MMTk page off the DRLVM core VM development page and put in
Weldon's list.
thank you many times! I tried to create the web page last week but the
network and the servers conspired against me.
On 10/23/06, Gregory Shimansky
All,
Just a few minutes ago I sent a mail titled, [DRLVM][MMTk] current status
and plan. It is way too long and detailed to include in this list of drlvm
enhancements. Below is a summary that hopefully is at the appropriate level
of detail. Please refer to the above email for more information.
On Monday 23 October 2006 20:21 Weldon Washburn wrote:
All,
Just a few minutes ago I sent a mail titled, [DRLVM][MMTk] current status
and plan. It is way too long and detailed to include in this list of
drlvm enhancements. Below is a summary that hopefully is at the
appropriate level of
For today my vision is:
* DRLVM TODOs is broken into Core VM TODOs and JIT TODOs
JIT TODOs are broken into For Beginners, Front End,
Performance, etc.
now implemented :) take a look
done. Now it's TODO List for DRLVM. JIT dev tasks link moved
there. Limitations enlisted there too. I hope,
On the 0x207 day of Apache Harmony Rana Dasgupta wrote:
Gregory had already created an entry on the front page ( see his comments
above ).
I expected to see JIT development tasks and DRLVM known issues and
limitations (TODO list for DRLVM) somewhat unified in naming. Say, I
prefer JIT
I don't really care about wording, I just wanted to make separate list for
high level TODO items, like implementation of big pieces, and
enhancements/limitations of the current code state. So I made a new link
from the page which Rana used and put there my 3 items. If you think
appropriate, you
On the 0x207 day of Apache Harmony Gregory Shimansky wrote:
I don't really care about wording, I just wanted to make separate list for
high level TODO items, like implementation of big pieces, and
enhancements/limitations of the current code state. So I made a new link
from the page which Rana
Egor Pasko wrote:
On the 0x207 day of Apache Harmony Gregory Shimansky wrote:
I don't really care about wording, I just wanted to make separate list for
high level TODO items, like implementation of big pieces, and
enhancements/limitations of the current code state. So I made a new link
from
On the 0x208 day of Apache Harmony Gregory Shimansky wrote:
Egor Pasko wrote:
On the 0x207 day of Apache Harmony Gregory Shimansky wrote:
I don't really care about wording, I just wanted to make separate list for
high level TODO items, like implementation of big pieces, and
On 18 Oct 2006 11:31:09 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
I think 2 more optimizations should find themselves in the list as
separate items, because they are easily formulated and are a good
chance for performance gains that Jitrino.OPT can offer:
+ Type Value Profiling in Jitrino.OPT
On the 0x206 day of Apache Harmony Rana Dasgupta wrote:
Egor,
I understand them as seperate and distinct optimizations, but we can do
it however you, Mikhail would like to list them. The list also does not
include more local optimizations that are bound to appear as a result of
performance
On 18 Oct 2006 13:50:02 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
I see, small items are not worth to mention.. right!
I see these 2 tasks as good candidates to list because they are:
* easily understood
* attractive to work on
* kind of critical for performance today
* not trivial, but
to be fixed to ensure the code runs and what needs
to be done to make it run better :)
Thank you,
Nadya Morozova
-Original Message-
From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 17, 2006 11:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] A list of drlvm
On the 0x206 day of Apache Harmony Mikhail Fursov wrote:
On 18 Oct 2006 11:31:09 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
I think 2 more optimizations should find themselves in the list as
separate items, because they are easily formulated and are a good
chance for performance gains
On the 0x206 day of Apache Harmony Egor Pasko wrote:
On the 0x206 day of Apache Harmony Mikhail Fursov wrote:
On 18 Oct 2006 11:31:09 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
I think 2 more optimizations should find themselves in the list as
separate items, because they are easily
On 18 Oct 2006 16:13:26 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
Let's mark in 2 categories: Novice and Advanced. Otherwise it
sounds like you should prove that you are an expert, only then you
can take the task, which I do not want to stress on.
Ok, moreover some tasks can have both
Alex,
Thanks for the information about Intel64 conventions for long mode. I
spoke losely and inaccurately below. I am the collector of the
development items, not the originator of all items :-) It may be a good
idea to write a short document describing the calling conventions we support
on
I added the VM dev tasks to
http://wiki.apache.org/harmony/CoreVmDevelopmentItems
off Gregory's currently empty page. Please change as necessary.
Rana
On 18 Oct 2006 20:11:14 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
now this is done:
On the 0x207 day of Apache Harmony Rana Dasgupta wrote:
I added the VM dev tasks to
http://wiki.apache.org/harmony/CoreVmDevelopmentItems
off Gregory's currently empty page. Please change as necessary.
Why not from the front page?
On 18 Oct 2006 20:11:14 +0700, Egor Pasko [EMAIL
Gregory had already created an entry on the front page ( see his comments
above ).
On 19 Oct 2006 10:55:43 +0700, Egor Pasko [EMAIL PROTECTED] wrote:
On the 0x207 day of Apache Harmony Rana Dasgupta wrote:
I added the VM dev tasks to
http://wiki.apache.org/harmony/CoreVmDevelopmentItems
Hi Gregory,
It is a good idea to put up a live list, thanks. Here are some
suggestions on the contents for development items in the VM/JIT. A few may
be almost done. We can fine tune...and add other work items as well
JIT Items
==
- GC related: WB support in Jitrino.opt
Implement
Rana,
the JIT list is really good. Thanks for collecting it.
I propose to create a single page for DRLVM tasks and list only components
on it. And for every component from the list create another page with its
tasks. The reason is that after Rana's post we have too much open tasks for
a single
Mikhail Fursov wrote:
Rana,
the JIT list is really good. Thanks for collecting it.
I propose to create a single page for DRLVM tasks and list only components
on it. And for every component from the list create another page with its
tasks. The reason is that after Rana's post we have too much
Mikhail,
Makes sense. BTW, we need to change the IA-64 to IPF( IA-64 is not an
external term ) on any posted list. IA32 to x86-32 bit and Intel 64 to
x86-64 bit. Sorry for the typo's.
Rana
On 10/17/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
Mikhail Fursov wrote:
Rana,
the JIT
On Tuesday 17 October 2006 19:26 Rana Dasgupta wrote:
Mikhail,
Makes sense. BTW, we need to change the IA-64 to IPF( IA-64 is not an
external term ) on any posted list. IA32 to x86-32 bit and Intel 64 to
x86-64 bit. Sorry for the typo's.
I agree with Mikhail, the list looks quite big with
Very comprehensive list and the GC part is also a good summary that
catches those in my mind.
We probably want to categorize the items into something like bugs,
limitations, enhancements and features wanted so that
contributors can have a clear picture on DRLVM functionalities.
Thanks,
xiaofeng
A small correction:
Currently the IA-32 and Intel-64 CG uses calling conventions
that pass all parameters on stack.
Stack-only is about IA-32 calling convention.
Intel64 CG generates a calling convention as per SystemV ABI
recommendations [1].
This is a variant of fastcall with 6 GP
Rana,
thank you for collecting it all together in one list!
I think 2 more optimizations should find themselves in the list as
separate items, because they are easily formulated and are a good
chance for performance gains that Jitrino.OPT can offer:
+ Type Value Profiling in Jitrino.OPT -
Hello
You know that drlvm was donated by Intel and there was some period of time
while drlvm was developed internally. We had an internal bugzilla server to
track the issues. In an effort to move all development to the open this
internal bugzilla will be closed.
The database is quite big and
Go for it.
Gregory Shimansky wrote:
Hello
You know that drlvm was donated by Intel and there was some period of time
while drlvm was developed internally. We had an internal bugzilla server to
track the issues. In an effort to move all development to the open this
internal bugzilla will be
Good idea. -xiaofeng
On 10/17/06, Gregory Shimansky [EMAIL PROTECTED] wrote:
Hello
You know that drlvm was donated by Intel and there was some period of time
while drlvm was developed internally. We had an internal bugzilla server to
track the issues. In an effort to move all development to
Once it's more or less ready let's point to that page from TODO on our website
Thanks,
Mikhail
2006/10/17, Gregory Shimansky [EMAIL PROTECTED]:
Hello
You know that drlvm was donated by Intel and there was some period of time
while drlvm was developed internally. We had an internal bugzilla
33 matches
Mail list logo
