On the 0x1F3 day of Apache Harmony Mikhail Fursov wrote: > Egor, > I think this is right suggestion to synchronize our WB and H1580 > implementations. AFAIK H1580 uses old JET version and is not > compatible with the latest compiler version.
Agreed. This patch is "before BBC" if this is what you mean. Need to test against a newer revision. Mikhail, I guess, it's you who are going to provide the committable version of the JET/WB patch. So it's up to you whether to update or reimplement... > If it's true, our implementation for the new JET/OPT version will do the job > for the both subprojects. > > The only question I have now is a question to Geir and other commiters: > Do I really need to create a new JIRA for WB support in Jitrino? Or is it > better to add my patches to H1580? > I ask this because the last time a person added a patch to the JIRA created > by me was asked by Geir to use another JIRA to separate our contributions (I > mean Jitrino.OPT testing framework). That makes me confused a little. Another question from me: Can I combine some patches and attach them back to JIRA listing all original contributors to the patch explicitly? If yes, I would be happy. If no, that makes it difficult to exchange ideas/code/etc. Are there any recommendations how to make effective development of a big feature (say, new ABCD or JIT-testing framework) a) by several people b) avoiding commits to SVN for a long time? ..sorry, not obvious to me, could not find the answer in Apache FAQs :( > > > On 29 Sep 2006 14:31:18 +0700, Egor Pasko <[EMAIL PROTECTED]> wrote: > > > > On the 0x1F3 day of Apache Harmony Mikhail Fursov wrote: > > > On 9/29/06, Weldon Washburn <[EMAIL PROTECTED]> wrote: > > > > > > > > Alex Astapchuk, Mikhail Fursov, > > > > > > > > With the patch blizzard of the last few weeks, Harmony-816 no longer > > > > works. > > > > The patches won't stick. Can you put harmony-816 back together? Or > > if it > > > > make sense, we can close this JIRA and open another one. In any case, > > I > > > > would like to make forward progress on MMTk port once again. I > > realize > > > > Jitrino.OPT now has write barrier and vmmagic support. I'd still like > > to > > > > keep Jitrino.JET functional. Its much easier to debug with > > JET. Also, I > > > > will get to Jitrino.OPT once I get MMTk moved over to the latest tree. > > > > > > Weldon, > > > You are right, the magics support code in H816 is not compatible with > > > updated JET version, but it will be fixed asap. > > > My plan is: > > > 1) Today: commit magic implementation for Jitrino.OPT (Oh end-of-quoter > > > period! I could do it a week ago :) ) > > > 2) Monday: commit updated magic implementation for Jitrino.JET > > > 3) Tuesday: commit WB implementation for Jitrino.JET > > > 4) Next week: resume helper inlining thread due to the fact magics are > > > ready. > > > > > > I going to create new JIRA issue with fresh updates. So H816 can be > > closed. > > > > Mikhail, maybe not update the WB impl, but use HARMONY-1850? I agree > > to Weldon anticipating LIL in there. We can eliminate LIL in 1850 > > quickly. > > > > -- > > Egor Pasko, Intel Managed Runtime Division > > > > > > --------------------------------------------------------------------- > > Terms of use : http://incubator.apache.org/harmony/mailing.html > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Mikhail Fursov -- Egor Pasko, Intel Managed Runtime Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
