Re: Questions about GSOC
chromatic wrote: If it's *close* (and mostly passing tests) we can always throw it back into trunk immediately after a monthly release and give ourselves 4 weeks to clean it up. The important thing to remember is that the GSOC project wasn't "revamp the GC system to meet the new spec" it was "implement a tri-color, incremental GC module for Parrot". Andrew did that, quite well. There's a separate milestone (funded by NLNet) for the full implementation, which includes integrating Andrew's work. Under the revised timeline, that milestone is due October 15th. We shouldn't rush to merge in code that isn't ready to merge. It will be merged, though, after some additional work. Andrew might be disappointed that he didn't reach the top of Mt. Everest, but he far exceeded our expectations, and congratulations are in order. Allison
Re: Questions about GSOC
On Wed, Aug 20, 2008 at 01:22:33PM -0400, Will Coleda wrote: > On Wed, Aug 20, 2008 at 1:15 PM, chromatic <[EMAIL PROTECTED]> wrote: > > The overall concepts of the incremental GC are solid, but a couple of > > details > > of the implementation need polishing. It's difficult to debug these types > > of > > problems, and even more difficult to estimate them. (In particular, > > interleaving GC headers and GC'd elements leads to some troublesome offset > > manipulation.) > You can always try to identify the chunks ex post facto and start the > merge back a chunk at a time; not as easy as identifying the bits > ahead of time, but doable. > If it's *close* (and mostly passing tests) we can always throw it back > into trunk immediately after a monthly release and give ourselves 4 > weeks to clean it up. Right now TGE fails to build, because the Integer PMCs stored in the interpreter class type registry get collected inappropriately. That's on GNU/Linux on x86, which is as forgiving as a platform gets. There are likely platform-specific bugs on PPC and Sparc and 64-bit platforms, not to mention with compilers other than GCC. Tracking down bugs and crashes to a specific checkin will be difficult. If we can figure out the class registry bug and get tests to pass reliably, we might be able to get more platform testing and consider a merge back. As it is now, it's riskier than I like. I don't want to block Rakudo, at least for more than overnight. -- c
Re: Questions about GSOC
On Wed, Aug 20, 2008 at 1:15 PM, chromatic <[EMAIL PROTECTED]> wrote: > On Wed, Aug 20, 2008 at 01:00:24PM +0300, Nikolay Ananiev wrote: > >> Today I saw Andrew's last post in his blog about the end of gsoc. >> Since I could not find much information about the NCI and GC projects I'm >> asking here: What's the status of these projects? >> Andrew's last post seems discouraging. How much of the new GC is completed? > > It's just about functionally complete, but there are a couple of > difficult-to-debug bugs remaining. I figured out one of them the other day, > but as with most new GC problems, it'll take a while to find and fix. > >> Are we going to have a new GC this year? > > Yes. > >> What are the main problems that remain and have to be solved? > > The overall concepts of the incremental GC are solid, but a couple of details > of the implementation need polishing. It's difficult to debug these types of > problems, and even more difficult to estimate them. (In particular, > interleaving GC headers and GC'd elements leads to some troublesome offset > manipulation.) > > It's not clear what the best approach to merging is; I should have encouraged > Andrew to work in smaller steps, such that he could run all of the tests after > each change and expect that they'd all pass. > > -- c > You can always try to identify the chunks ex post facto and start the merge back a chunk at a time; not as easy as identifying the bits ahead of time, but doable. If it's *close* (and mostly passing tests) we can always throw it back into trunk immediately after a monthly release and give ourselves 4 weeks to clean it up. -- Will "Coke" Coleda
Re: Questions about GSOC
On Wed, Aug 20, 2008 at 01:00:24PM +0300, Nikolay Ananiev wrote: > Today I saw Andrew's last post in his blog about the end of gsoc. > Since I could not find much information about the NCI and GC projects I'm > asking here: What's the status of these projects? > Andrew's last post seems discouraging. How much of the new GC is completed? It's just about functionally complete, but there are a couple of difficult-to-debug bugs remaining. I figured out one of them the other day, but as with most new GC problems, it'll take a while to find and fix. > Are we going to have a new GC this year? Yes. > What are the main problems that remain and have to be solved? The overall concepts of the incremental GC are solid, but a couple of details of the implementation need polishing. It's difficult to debug these types of problems, and even more difficult to estimate them. (In particular, interleaving GC headers and GC'd elements leads to some troublesome offset manipulation.) It's not clear what the best approach to merging is; I should have encouraged Andrew to work in smaller steps, such that he could run all of the tests after each change and expect that they'd all pass. -- c
Re: Questions about GSOC
gsoc_nci code is available in branches/gsoc_nci_001 jitted nci stubs works on i386 WIN32 and i386 LINUX Its probably going to be merged this week. Kevin Nikolay Ananiev wrote: Hey guys, Today I saw Andrew's last post in his blog about the end of gsoc. Since I could not find much information about the NCI and GC projects I'm asking here: What's the status of these projects? Andrew's last post seems discouraging. How much of the new GC is completed? Are we going to have a new GC this year? What are the main problems that remain and have to be solved? And about the NCI project... I couldn't find any information about it. What's going on there?
Questions about GSOC
Hey guys, Today I saw Andrew's last post in his blog about the end of gsoc. Since I could not find much information about the NCI and GC projects I'm asking here: What's the status of these projects? Andrew's last post seems discouraging. How much of the new GC is completed? Are we going to have a new GC this year? What are the main problems that remain and have to be solved? And about the NCI project... I couldn't find any information about it. What's going on there?
