« Return to Thread: [rvm-core] Code freeze
Re: [rvm-core] Code freeze
by Ian Rogers (nabble)
::
Rate this Message:
2009/2/3 Steve Blackburn <Steve.Blackburn@...>:
>
> On 04/02/2009, at 2:50 AM, David P Grove wrote:
>
>> improvements to the documentation, method names, etc. I'd prefer to
>> avoid making those changes to the trunk.
>
> I disagree. I would strongly prefer to see the branch merged in as soon as
> it is fully functional and deal with any cleanups in documentation in the
> trunk. PNT represents a major increase of functionality for Jikes RVM on
> AIX (where our syscall interception strategy doesn't work) and I'm very
> interested in having this available. I also think there may be a
> significant increase in our chances to get a 2009 SoC project if at least
> one of the 2008 projects had been successfully mainlined.
>
> I agree with Dave.
> We need to get native threads happening ASAP for a host of strategic
> reasons.
> To make that happen, Tony has paid for Fil to make the journey to ANU and
> work intensively with Daniel. Meanwhile Daniel has put his PhD write-up on
> ice for two weeks for the same reason.
> Since Fil arrived, the progress has been dramatic. After two days they
> had the native threads branch go from 219/2184 to 11/2184. This is very
> close to the head in terms of stability (see most recent kumataka regression
> result). Since then they've pushed on PPC and nailed a few more bugs (see
> recent commit messages to see the progress they've made on PPC). Daniel is
> kicking off another kumataka run now. So we are now finally very close to
> having native threads production-ready.
> --Steve
Firstly, this is great. It's unfortunate that expense and Daniel's
time has come into it. I'm sure Tony and Fil have told you about the
work merging up done in Kent.
My concern is less about that we'll have something that works and more
that we've regressed in a number of areas that I have spent time and
effort improving. In particular to make the threading model
intelligible. I think with a "quality review" the state of the code in
the PNT branch could be significantly improved. We can lose misleading
concepts like "nicely" and "dangerously" and get back to describing
methods for what they do. We can also decrease the visibility of
fields (good practice and better encapsulation).
Ian
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core
>
> On 04/02/2009, at 2:50 AM, David P Grove wrote:
>
>> improvements to the documentation, method names, etc. I'd prefer to
>> avoid making those changes to the trunk.
>
> I disagree. I would strongly prefer to see the branch merged in as soon as
> it is fully functional and deal with any cleanups in documentation in the
> trunk. PNT represents a major increase of functionality for Jikes RVM on
> AIX (where our syscall interception strategy doesn't work) and I'm very
> interested in having this available. I also think there may be a
> significant increase in our chances to get a 2009 SoC project if at least
> one of the 2008 projects had been successfully mainlined.
>
> I agree with Dave.
> We need to get native threads happening ASAP for a host of strategic
> reasons.
> To make that happen, Tony has paid for Fil to make the journey to ANU and
> work intensively with Daniel. Meanwhile Daniel has put his PhD write-up on
> ice for two weeks for the same reason.
> Since Fil arrived, the progress has been dramatic. After two days they
> had the native threads branch go from 219/2184 to 11/2184. This is very
> close to the head in terms of stability (see most recent kumataka regression
> result). Since then they've pushed on PPC and nailed a few more bugs (see
> recent commit messages to see the progress they've made on PPC). Daniel is
> kicking off another kumataka run now. So we are now finally very close to
> having native threads production-ready.
> --Steve
Firstly, this is great. It's unfortunate that expense and Daniel's
time has come into it. I'm sure Tony and Fil have told you about the
work merging up done in Kent.
My concern is less about that we'll have something that works and more
that we've regressed in a number of areas that I have spent time and
effort improving. In particular to make the threading model
intelligible. I think with a "quality review" the state of the code in
the PNT branch could be significantly improved. We can lose misleading
concepts like "nicely" and "dangerously" and get back to describing
methods for what they do. We can also decrease the visibility of
fields (good practice and better encapsulation).
Ian
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core
« Return to Thread: [rvm-core] Code freeze
| Free embeddable forum powered by Nabble | Forum Help |
