harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Loenko" <mloe...@gmail.com>
Subject Re: [general] Deciding a date for Milestone 4
Date Mon, 03 Dec 2007 08:39:21 GMT
Right

2007/11/30, Tim Ellison <t.p.ellison@gmail.com>:
> I see HARMONY-5098 has been committed.  AFAIK there are no more major
> changes due for this milestone iteration from anyone, right?
>
> Regards,
> Tim
>
> Ilya Berezhniuk wrote:
> > Moreover, HARMONY-5098 is the last chunk to add uncompressed
> > references support to GC_GEN.
> >
> > Other components (VM and JITs) are already corrected to support
> > uncompressed references, and those changes did not introduce any
> > regressions.
> >
> > 2007/11/28, Rana Dasgupta <rdasgupt@gmail.com>:
> >> I think that we should feel quite confident about it. All tests etc.pass at
> >> this point, if we find bugs with larger benchmarks/apps, we will fix them.
> >> So we should be OK :-)
> >>
> >> Rana
> >>
> >> On Nov 28, 2007 8:51 AM, Tim Ellison <t.p.ellison@gmail.com> wrote:
> >>
> >>> Rana Dasgupta wrote:
> >>>>  One of the new features in DRLVM in this milestone is support for
> >>> native 64
> >>>> bit references( we only supported 32 bit compressed references on 64
bit
> >>>> architecture before and therefore accessibility upto 4GB ). Almost all
> >>> the
> >>>> feature work is done and committed The pending change is in
> >>> Harmony-5098.
> >>>> Pretty sure that it will be done reviewing/changes and will get
> >>> committed by
> >>>> Nov 30, but it may spill over by a day or two. Just a heads up.
> >>> Is this something we (collectively) are happy to put in at the last
> >>> minute?  Is it something you would prefer people to use for a few weeks
> >>> before declaring good enough for a milestone build?
> >>>
> >>> There should be no shame in moving it into the next milestone (which is
> >>> why we want to hold them quite frequently, but I won't go on about that
> >>> again :-) ).
> >>>
> >>> Regards,
> >>> Tim
> >>>
> >>>
> >
> >
>

Mime
View raw message