at http://www.mirandabanda.org/files/Cog/VM/VM.r2714/
These fix quite a serious bug with the JIT that would cause crashes in large images.
CogVM binaries as per VMMaker.oscog-eem.282/r2714
Change application name from Croquet to Squeak and change to green Cog Squeak icons. Add accurate version info to the Windows exes (include SCCSID in properties).
Add the SSLPlugin on mac and linux (won't link on old mingw; need to update).
Cogit: Fix *HORRIBLE* yet ancient bug with the CogObjectRep. Both CogObjectRepresentationForSqueakV3>>couldBeObject: & CogObjectRepresentationForSqueakV3>>shouldAnnotateObjectReference: used signed comparisons for oops and so once the heap size pushes oops into the upper half of the address space constant oops in machine code were no longer being updated by the GC.
StackInterpreter: rewrite the login for printing methods so that printing the frame of a bad receiver won't seg fault.
Add primitivePathToUsing which mimics the PointerFinder and can hence be used to debug or verify it.
Remove unnecessary forceInterruptCheck in NewObjectMemory>>become:with:twoWay:copyHash:. (heartbeat does this for us).
Fix bug in assert in NewCoObjectMemory>>restoreHeaderOf:to:.
Slang: Fix translation of to:by:do: loops so that the limit is not re-evaluated on each iteration if it may have side-effects.
Include the correct AioPlugin (UnixAioPlugin)
Include SqueakSSLPlugin in the configurations.
Cogit: Stop reporting EncounteredUnknownBytecode with an error message.
Fix slip in ceSICMiss: that didn't link new PIC if an MNU case.
Add pixel peeker prims to BitBltPlugin. Minor signature changes to BitBltPlugin & HostWindowPlugin from SmartSyntaxPluginGenerator bug fix.
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
On Thu, Apr 4, 2013 at 3:14 PM, Eliot Miranda eliot.miranda@gmail.com wrote:
at http://www.mirandabanda.org/files/Cog/VM/VM.r2714/
These fix quite a serious bug with the JIT that would cause crashes in large images.
CogVM binaries as per VMMaker.oscog-eem.282/r2714
Change application name from Croquet to Squeak and change to green Cog Squeak icons. Add accurate version info to the Windows exes (include SCCSID in properties).
Add the SSLPlugin on mac and linux (won't link on old mingw; need to update).
Cogit: Fix *HORRIBLE* yet ancient bug with the CogObjectRep. Both CogObjectRepresentationForSqueakV3>>couldBeObject: & CogObjectRepresentationForSqueakV3>>shouldAnnotateObjectReference: used signed comparisons for oops and so once the heap size pushes oops into the upper half of the address space constant oops in machine code were no longer being updated by the GC.
StackInterpreter: rewrite the login for printing methods so that printing the frame of a bad receiver won't seg fault.
Add primitivePathToUsing which mimics the PointerFinder and can hence be used to debug or verify it.
Remove unnecessary forceInterruptCheck in NewObjectMemory>>become:with:twoWay:copyHash:. (heartbeat does this for us).
Fix bug in assert in NewCoObjectMemory>>restoreHeaderOf:to:.
Slang: Fix translation of to:by:do: loops so that the limit is not re-evaluated on each iteration if it may have side-effects.
Include the correct AioPlugin (UnixAioPlugin)
Include SqueakSSLPlugin in the configurations.
Cogit: Stop reporting EncounteredUnknownBytecode with an error message.
Fix slip in ceSICMiss: that didn't link new PIC if an MNU case.
Add pixel peeker prims to BitBltPlugin. Minor signature changes to BitBltPlugin & HostWindowPlugin from SmartSyntaxPluginGenerator bug fix.
-- best, Eliot
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
On Thu, Apr 4, 2013 at 3:14 PM, Eliot Miranda eliot.miranda@gmail.com wrote:
at http://www.mirandabanda.org/files/Cog/VM/VM.r2714/
These fix quite a serious bug with the JIT that would cause crashes in
large
images.
CogVM binaries as per VMMaker.oscog-eem.282/r2714
Change application name from Croquet to Squeak and change to green Cog Squeak icons. Add accurate version info to the Windows exes (include SCCSID in properties).
Add the SSLPlugin on mac and linux (won't link on old mingw; need to update).
Cogit: Fix *HORRIBLE* yet ancient bug with the CogObjectRep. Both CogObjectRepresentationForSqueakV3>>couldBeObject: & CogObjectRepresentationForSqueakV3>>shouldAnnotateObjectReference: used signed comparisons for oops and so once the heap size pushes oops into the upper half of the address space constant oops in machine code were no longer being updated by the GC.
StackInterpreter: rewrite the login for printing methods so that printing the frame of a bad receiver won't seg fault.
Add primitivePathToUsing which mimics the PointerFinder and can hence be used to debug or verify it.
Remove unnecessary forceInterruptCheck in NewObjectMemory>>become:with:twoWay:copyHash:. (heartbeat does this for us).
Fix bug in assert in NewCoObjectMemory>>restoreHeaderOf:to:.
Slang: Fix translation of to:by:do: loops so that the limit is not re-evaluated on each iteration if it may have side-effects.
Include the correct AioPlugin (UnixAioPlugin)
Include SqueakSSLPlugin in the configurations.
Cogit: Stop reporting EncounteredUnknownBytecode with an error message.
Fix slip in ceSICMiss: that didn't link new PIC if an MNU case.
Add pixel peeker prims to BitBltPlugin. Minor signature changes to BitBltPlugin & HostWindowPlugin from SmartSyntaxPluginGenerator bug fix.
-- best, Eliot
Am 07.04.2013 um 01:30 schrieb Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Best -Tobias
On Sun, Apr 7, 2013 at 11:01 PM, Tobias Pape Das.Linux@gmx.de wrote:
Am 07.04.2013 um 01:30 schrieb Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com
wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named
archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I
stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Oops. It is indeed YEAR.WEEK.ID. I misspoke. Here's the command that delivers the tag:
REV=`grep 'SvnRawRevisionString.*Rev:' platforms/Cross/vm/sqSCCSVersion.h \ | sed 's/^.*Rev: ([0-9][0-9]*) $";/\1/'` TAG=`date +%g.%U.`$REV
Best -Tobias
On 8 April 2013 17:36, Eliot Miranda eliot.miranda@gmail.com wrote:
On Sun, Apr 7, 2013 at 11:01 PM, Tobias Pape Das.Linux@gmx.de wrote:
Am 07.04.2013 um 01:30 schrieb Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Oops. It is indeed YEAR.WEEK.ID. I misspoke. Here's the command that delivers the tag:
REV=`grep 'SvnRawRevisionString.*Rev:' platforms/Cross/vm/sqSCCSVersion.h \ | sed 's/^.*Rev: ([0-9][0-9]*) $";/\1/'` TAG=`date +%g.%U.`$REV
The CI build scripts are duly updated.
frank
Best -Tobias
-- best, Eliot
I thought the "sequence number" (for lack of a better term), e.g., 2714, was what made the names unique. If not, is it still needed too?
On Mon, Apr 8, 2013 at 11:36 AM, Eliot Miranda eliot.miranda@gmail.com wrote:
On Sun, Apr 7, 2013 at 11:01 PM, Tobias Pape Das.Linux@gmx.de wrote:
Am 07.04.2013 um 01:30 schrieb Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Oops. It is indeed YEAR.WEEK.ID. I misspoke. Here's the command that delivers the tag:
REV=`grep 'SvnRawRevisionString.*Rev:' platforms/Cross/vm/sqSCCSVersion.h \ | sed 's/^.*Rev: ([0-9][0-9]*) $";/\1/'` TAG=`date +%g.%U.`$REV
Best -Tobias
-- best, Eliot
On 08.04.2013, at 10:31, Chris Muller asqueaker@gmail.com wrote:
I thought the "sequence number" (for lack of a better term), e.g., 2714, was what made the names unique. If not, is it still needed too?
On Mon, Apr 8, 2013 at 11:36 AM, Eliot Miranda eliot.miranda@gmail.com wrote:
On Sun, Apr 7, 2013 at 11:01 PM, Tobias Pape Das.Linux@gmx.de wrote:
Am 07.04.2013 um 01:30 schrieb Eliot Miranda eliot.miranda@gmail.com:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Oops. It is indeed YEAR.WEEK.ID. I misspoke. Here's the command that delivers the tag:
REV=`grep 'SvnRawRevisionString.*Rev:' platforms/Cross/vm/sqSCCSVersion.h \ | sed 's/^.*Rev: ([0-9][0-9]*) $";/\1/'` TAG=`date +%g.%U.`$REV
Doesn't make sense to me. Builds should be reproducible, so why encode the build date in the file name? If you really need it, then the SVN version should take precedence over the build date. So "id-date" would be better, grouping same sources but different build dates together.
- Bert -
On Mon, Apr 8, 2013 at 10:38 AM, Bert Freudenberg bert@freudenbergs.dewrote:
On 08.04.2013, at 10:31, Chris Muller asqueaker@gmail.com wrote:
I thought the "sequence number" (for lack of a better term), e.g., 2714, was what made the names unique. If not, is it still needed too?
On Mon, Apr 8, 2013 at 11:36 AM, Eliot Miranda eliot.miranda@gmail.com
wrote:
On Sun, Apr 7, 2013 at 11:01 PM, Tobias Pape Das.Linux@gmx.de wrote:
Am 07.04.2013 um 01:30 schrieb Eliot Miranda <eliot.miranda@gmail.com
:
On Thu, Apr 4, 2013 at 1:53 PM, Chris Muller asqueaker@gmail.com
wrote:
Woo hoo! Thanks Eliot!
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named
archive-WEEK.YEAR.SVNID.ext.
Hope that's not too inconvenient. But they need unique names. I
stupidly overwrite a set of old files doing some reorganization a few weeks back and that wouldn't have happened with unique names...
I think this is pretty useful, however, what about
archive-YEAR.WEEK.ID.ext
? That way, the vms are ordered successively :) (as the current one is 13.13.… changing shouldn't be a problem ;))
Oops. It is indeed YEAR.WEEK.ID. I misspoke. Here's the command
that delivers the tag:
REV=`grep 'SvnRawRevisionString.*Rev:'
platforms/Cross/vm/sqSCCSVersion.h \
| sed 's/^.*Rev: \([0-9][0-9]*\) $";/\1/'`
TAG=`date +%g.%U.`$REV
Doesn't make sense to me. Builds should be reproducible, so why encode the build date in the file name? If you really need it, then the SVN version should take precedence over the build date. So "id-date" would be better, grouping same sources but different build dates together.
It's not to do with the build. It's just a name to package it in. -- Eliot
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named archive-WEEK.YEAR.SVNID.ext.
Why not just us the ISO standard date format? Thus archive-20130408-version etc
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: MAW: Make Aggravating Whine
On Mon, Apr 8, 2013 at 10:00 AM, tim Rowledge tim@rowledge.org wrote:
Quick question, I see you're using a new naming convention, what does 13.13 mean?
It means the 13th week of 2013. So all the archives are named
archive-WEEK.YEAR.SVNID.ext.
Why not just us the ISO standard date format? Thus archive-20130408-version etc
Because the convention follows one adopted for the Newspeak builds, which derives from a Microsoft convention.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: MAW: Make Aggravating Whine
vm-dev@lists.squeakfoundation.org