Re: [Squeak-VMdev] Newest VMMaker to try out

[Dan I. <Da...@Sq...>]

>How's the 64bit stuff going? Any changes that are worth putting into
>general release VMMaker?

Not at this point.  There will be a huge pile after a while.  I hope to put out a general update in a week or 10 days.

>I got bitten by the oop>2gb problem this week. Your(?) code for
>checking for acceptable classes when loading an image segment goes nuts
>if fed an oop it thinks is -ve. Don't suppose you've done any work that
>might fix some of these places? Hate to waste time duplicating work.

The first work that we (mainly Ian right now) are doing is to generalize the kernel interpreter so that it can run any combination of 32- or 64-bit image on 32- or 64-bit machine.  This means being careful about the types of pointers, small integers and other quantities such as bytes, 16-, 32- and 64-bit ints.

Other than through general code review, we would not find such a problem as that to which you allude, as it is particular to images that are close to their maximum oop size.  Your 32-bit image is a valuable example, and it's not likely that we'll find a 64-bit image with this problem for a while.

Therefore:  please *do* look into fixing it or forwarding it to me for attention, and we'll make sure to incorporate it with out other changes.

Thanks
	- Dan