harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov" <alexey.v.varla...@gmail.com>
Subject Re: [drlvm] IPF functionality
Date Mon, 16 Oct 2006 06:46:24 GMT
2006/10/16, Mikhail Loenko <mloenko@gmail.com>:
> 2006/10/14, Tim Ellison <t.p.ellison@gmail.com>:
> > Just to add my 2p -- I also agree with doing the work in the trunk.  Of
> > course the minimum cost of working there is that you do no harm to the
> > other platforms.  That is the zeroth level of integration.
> >
> > The first level of integration would then be to modify the build system
> > to build the IPF code, and of course it has to compile, know it's
> > dependencies, etc. etc.
> >
> > Until the code can run some useful tests it is probably worth going on
> > to run only a restricted set of the tests we have and then take on more.
> >
> > We can be bringing a number of new platforms on line simultaneously this
> > way, with each potentially being at a different level of
> > integration/maturity within the project.
>
> When we bring new platforms how will we make sure that a patch for some
> rare platform would not break another one?

Supposed we can charge CC on all supported platforms:

while (!passed.on.available platforms) {
   defer patch & discuss;
}
do commit;
if (some.platform.CC.failed) {
   rollback or fix ASAP;
}


>
> Thanks,
> Mikhail
>
> >
> > Regards,
> > Tim
> >
> > Rana Dasgupta wrote:
> > > On 10/13/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
> > >
> > >
> > >> >
> > >> > > This is just one more argument for doing IPF porting in a separate
> > >> > branch,
> > >> > > at least since some point.
> > >> > >
> > >> > > I admit that maintaining quality and checking for regressions
on new
> > >> > > platforms is a separate big problem but I believe we could try
to
> > >> > avoid it
> > >> > > during "incubation" of new platforms.
> > >> > >
> > >> > > Overall I agree we could wait with branch creation until real
> > >> problems
> > >> > > appear.
> > >> > >
> > >> >
> > >> > Great
> > >>
> > >>
> > > OK, we can then continue as is until the IPF port matures and is ready for
> > > running non trivial applications or performance tests. At that point we can
> > > decide whether to treat it as a primary platform, in which case, we will
> > > need to test on it before committing submissions to the main branch. Or
> > > secondary, in which case we branch it and let the IPF submitters control
> > > their own destiny.
> > >
> > > Thanks for the good comments.
> > >
> > > Rana
> > >
> > >
> > >
> > >
> > >
> > >> ---------------------------------------------------------------------
> > >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> > >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> > >>
> > >>
> > >
> >
> > --
> >
> > Tim Ellison (t.p.ellison@gmail.com)
> > IBM Java technology centre, UK.
> >
> >
> > ---------------------------------------------------------------------
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message