Integrating VMMaker-dtl.175

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Integrating VMMaker-dtl.175

Igor Stasenko
Dear all,

i would really like to finish an integration of new finalization.
But this requires releasing a new VMs for all platforms.

If you think, we're done with VM-side part, then lets proceed with
releasing new VMs, so we could start using new feature.

--
Best regards,
Igor Stasenko AKA sig.

Reply | Threaded
Open this post in threaded view
|

Re: Integrating VMMaker-dtl.175

David T. Lewis
On Thu, May 27, 2010 at 12:02:17PM +0300, Igor Stasenko wrote:
> Dear all,
>
> i would really like to finish an integration of new finalization.
> But this requires releasing a new VMs for all platforms.
>
> If you think, we're done with VM-side part, then lets proceed with
> releasing new VMs, so we could start using new feature.

One thing I want to ask before proceeding too far: I made a large
number of small changes in VMMaker-dtl.173 and VMMaker-dtl.174. These
are to ompile a VM for either 32-bit or 64-bit image from a single
generated code base.

Do these changes cause problems for anyone else? Especially, do they
make COG integration difficult? Or any other VM development projects
that are relying on VMMaker not being changed too much?

I don't expect this to be a problem, but I don't want to assume it
without asking.

Thanks,

Dave


Reply | Threaded
Open this post in threaded view
|

Re: Integrating VMMaker-dtl.175

Eliot Miranda-2
Hi David,

On Thu, May 27, 2010 at 5:01 AM, David T. Lewis <[hidden email]> wrote:
On Thu, May 27, 2010 at 12:02:17PM +0300, Igor Stasenko wrote:
> Dear all,
>
> i would really like to finish an integration of new finalization.
> But this requires releasing a new VMs for all platforms.
>
> If you think, we're done with VM-side part, then lets proceed with
> releasing new VMs, so we could start using new feature.

One thing I want to ask before proceeding too far: I made a large
number of small changes in VMMaker-dtl.173 and VMMaker-dtl.174. These
are to ompile a VM for either 32-bit or 64-bit image from a single
generated code base.

Do these changes cause problems for anyone else? Especially, do they
make COG integration difficult? Or any other VM development projects
that are relying on VMMaker not being changed too much?

The Cog changes are substantial and any additional changes to the base VMMaker for 64-bit will likely not add to the difficulty of the merge.  We'll have to go back to the common ancestor of current Squeak VMMaker and Cog and sift out fixes from new functionality, and I expect it to take some effort.  So please don't worry about the effect on Cog and keep making improvements.

best
Eliot 

I don't expect this to be a problem, but I don't want to assume it
without asking.

Thanks,

Dave