There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
But what to do with this??
Compiler reporting 'stack including temps is too deep'.
GeniePlugin>>primSameClassAbsoluteStrokeDistanceMyPoints: myPointsOop otherPoints: otherPointsOop myVectors: myVectorsOop otherVectors: otherVectorsOop mySquaredLengths: mySquaredLengthsOop otherSquaredLengths: otherSquaredLengthsOop myAngles: myAnglesOop otherAngles: otherAnglesOop maxSizeAndReferenceFlag: maxSizeAndRefFlag rowBase: rowBaseOop rowInsertRemove: rowInsertRemoveOop rowInsertRemoveCount: rowInsertRemoveCountOop
(yes, this is a method's message pattern) :)
i stopped trying to load VMMaker at this method.
It would be nice to have VMMaker loaded in image+closures running under VM+closures :)
On Thu, Apr 30, 2009 at 8:43 AM, Igor Stasenko siguctua@gmail.com wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
But what to do with this??
Compiler reporting 'stack including temps is too deep'.
GeniePlugin>>primSameClassAbsoluteStrokeDistanceMyPoints: myPointsOop otherPoints: otherPointsOop myVectors: myVectorsOop otherVectors: otherVectorsOop mySquaredLengths: mySquaredLengthsOop otherSquaredLengths: otherSquaredLengthsOop myAngles: myAnglesOop otherAngles: otherAnglesOop maxSizeAndReferenceFlag: maxSizeAndRefFlag rowBase: rowBaseOop rowInsertRemove: rowInsertRemoveOop rowInsertRemoveCount: rowInsertRemoveCountOop
(yes, this is a method's message pattern) :)
i stopped trying to load VMMaker at this method.
The workaround for this is just to change the code in generate: so one can proceed from the error and still define the method. The method doesn't need to be run, only translated so there's no harm in that. Some time some kind soul should refactor this method into an outer and an inner or I should change the large context sizes.
It would be nice to have VMMaker loaded in image+closures running
under VM+closures :)
Just do the workaround and you'll have just that.
-- Best regards, Igor Stasenko AKA sig.
On Thu, Apr 30, 2009 at 8:52 AM, Eliot Miranda eliot.miranda@gmail.comwrote:
On Thu, Apr 30, 2009 at 8:43 AM, Igor Stasenko siguctua@gmail.com wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
But what to do with this??
Compiler reporting 'stack including temps is too deep'.
GeniePlugin>>primSameClassAbsoluteStrokeDistanceMyPoints: myPointsOop otherPoints: otherPointsOop myVectors: myVectorsOop otherVectors: otherVectorsOop mySquaredLengths: mySquaredLengthsOop otherSquaredLengths: otherSquaredLengthsOop myAngles: myAnglesOop otherAngles: otherAnglesOop maxSizeAndReferenceFlag: maxSizeAndRefFlag rowBase: rowBaseOop rowInsertRemove: rowInsertRemoveOop rowInsertRemoveCount: rowInsertRemoveCountOop
(yes, this is a method's message pattern) :)
i stopped trying to load VMMaker at this method.
The workaround for this is just to change the code in generate: so one can proceed from the error and still define the method. The method doesn't need to be run, only translated so there's no harm in that. Some time some kind soul should refactor this method into an outer and an inner or I should change the large context sizes.
It would be nice to have VMMaker loaded in image+closures running
under VM+closures :)
Just do the workaround and you'll have just that.
and I should say we'll sort out a proper solution soon :)
-- Best regards, Igor Stasenko AKA sig.
2009/4/30 Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 30, 2009 at 8:43 AM, Igor Stasenko siguctua@gmail.com wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
But what to do with this??
Compiler reporting 'stack including temps is too deep'.
GeniePlugin>>primSameClassAbsoluteStrokeDistanceMyPoints: myPointsOop otherPoints: otherPointsOop myVectors: myVectorsOop otherVectors: otherVectorsOop mySquaredLengths: mySquaredLengthsOop otherSquaredLengths: otherSquaredLengthsOop myAngles: myAnglesOop otherAngles: otherAnglesOop maxSizeAndReferenceFlag: maxSizeAndRefFlag rowBase: rowBaseOop rowInsertRemove: rowInsertRemoveOop rowInsertRemoveCount: rowInsertRemoveCountOop
(yes, this is a method's message pattern) :)
i stopped trying to load VMMaker at this method.
The workaround for this is just to change the code in generate: so one can proceed from the error and still define the method. The method doesn't need to be run, only translated so there's no harm in that. Some time some kind soul should refactor this method into an outer and an inner or I should change the large context sizes.
Changing the code in #generate: will buy us nothing, because this error thrown when MC loads a package in image, and naturally, tries to compile & install all methods from it :)
It would be nice to have VMMaker loaded in image+closures running under VM+closures :)
Just do the workaround and you'll have just that.
-- Best regards, Igor Stasenko AKA sig.
On Thu, Apr 30, 2009 at 8:59 AM, Igor Stasenko siguctua@gmail.com wrote:
2009/4/30 Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 30, 2009 at 8:43 AM, Igor Stasenko siguctua@gmail.com
wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
But what to do with this??
Compiler reporting 'stack including temps is too deep'.
GeniePlugin>>primSameClassAbsoluteStrokeDistanceMyPoints: myPointsOop otherPoints: otherPointsOop myVectors: myVectorsOop otherVectors: otherVectorsOop mySquaredLengths: mySquaredLengthsOop otherSquaredLengths: otherSquaredLengthsOop myAngles: myAnglesOop otherAngles: otherAnglesOop maxSizeAndReferenceFlag: maxSizeAndRefFlag rowBase: rowBaseOop rowInsertRemove: rowInsertRemoveOop rowInsertRemoveCount: rowInsertRemoveCountOop
(yes, this is a method's message pattern) :)
i stopped trying to load VMMaker at this method.
The workaround for this is just to change the code in generate: so one
can proceed from the error and still define the method. The method doesn't need to be run, only translated so there's no harm in that. Some time some kind soul should refactor this method into an outer and an inner or I should change the large context sizes.
Changing the code in #generate: will buy us nothing, because this error thrown when MC loads a package in image, and naturally, tries to compile & install all methods from it :)
Once you have it in the image Monticello won't try and recompile it if it doesn't change. This is a one-time pain per image.
Another workaround is just to move the GeniePlugin somewhere else.
It would be nice to have VMMaker loaded in image+closures running under VM+closures :)
Just do the workaround and you'll have just that.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.
2009/4/30 Andreas Raab andreas.raab@gmx.de:
Eliot Miranda wrote:
Once you have it in the image Monticello won't try and recompile it if it doesn't change. This is a one-time pain per image.
Another workaround is just to move the GeniePlugin somewhere else.
To trash? As to me, this plugin is quite useless. Just a single bloated primitive, trying to do something .. can't guess what. Is it interface to some kind of device/ library?
That's what we've done for our images.
Cheers, - Andres
On Thu, Apr 30, 2009 at 06:43:00PM +0300, Igor Stasenko wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
The easy and quick fix is in VMMaker-dtl.121 on SqS.
Dave
Excellent, thanks David!
- A.
David T. Lewis wrote:
On Thu, Apr 30, 2009 at 06:43:00PM +0300, Igor Stasenko wrote:
There are multiple issues, when loading VMMaker into closure-aware image (10292).
two #needsToRegenerateInterpreterFile methods storing into block args. Fix is easy and quick.
The easy and quick fix is in VMMaker-dtl.121 on SqS.
Dave
vm-dev@lists.squeakfoundation.org
-
Andreas Raab -
David T. Lewis -
Eliot Miranda -
Igor Stasenko