- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Help menu disappeared [WAS] [ANN] Pharo-1.1-11400-rc1dev10.06.1

by laurent laffont

On Fri, Jun 18, 2010 at 12:29 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Just a meta remark... > > In this thread 8 people have sent a total of 30 mails. But in the end > nobody volunteers to do the (not very hard) work to make what was discussed > actually happen. Was this a bikeshed.com discussion? Maybe not since > designing good menus is complex and important. But my point is that we > should take care, as a community, to not only invest into discussions but at > least as much into *doing*. > You're right, but for my part I *hate* saying "I will do" and then don't find the courage/motivation/whatever and not doing it (especially when something else captures my energy, I'm suspicious of myself :). That said I've reached the first step I want on Autotest, so now I can work on the menus, I know how it works. Cheers, Laurent > > Cheers, > Adrian > > > > On Jun 16, 2010, at 08:42 , Adrian Lienhard wrote: > > > OK, since there seems no opposition lets change it as proposed. > > > > Any taker? > > > > Adrian > > > > On Jun 15, 2010, at 09:17 , StÃ©phane Ducasse wrote: > > > >> > >> On Jun 14, 2010, at 10:07 PM, Adrian Lienhard wrote: > >> > >>> OK, Torsten has some good points (like, why not doing it right now > rather than later?)! I took the proposal of Torsten from an earlier mail and > tweaked it a bit. This shows the complete world menu including sub menus: > >>> > >>> System Browser > >>> Workspace > >>> Test Runner > >>> Monticello Browser > >>> -------------------- > >>> Tools > >>> ... (<-as today) > >>> Windows > >>> Collapse all windows > >>> Expand all windows > >>> Close top window <<<< we could remove that since you can also press > the button > >>> Close all debuggers > >>> Send top window to back > >>> Move window onscreen > >>> Delete unchanged windows > >>> System > >>> About... > >>> Settings > >>> -------------- > >>> VM statistics > >>> Start profiling all processes > >>> Start profiling UI > >>> -------------- > >>> Start drawing again > >>> Start stepping again > >>> -------------- > >>> Restore display > >>> Enable halt inspect once > >>> Help > >>> Help Browser > >>> ProfStef Tutorial > >>> Welcome Workspace > >>> ---------------- > >>> Save > >>> Save as... > >>> Save and quit > >>> Quit > >>> > >>> > >>> Note, I inlined the debug menu into System. The reason is that I don't > like multiply nested menus and the system menu does not get overly long. > Also I deleted "Space left". Maybe other items like "Start stepping again" > are also not really useful anymore? Furthermore I moved "Close all > debuggers" into the Windows menu. I kept About... in system as I think it > has not much to do with Help but more with System. I also changed the labels > of some of the items (like Help Browser and ProfStef Tutorial). > >>> > >>> Does that look reasonable? > >>> > >>> Cheers, > >>> Adrian > >>> > >>> On Jun 14, 2010, at 20:45 , StÃ©phane Ducasse wrote: > >>> > >>>> torsten > >>>> > >>>> propose a menu redistribution as laurent did so that we arrive to > something better. > >>>> I agree that debug could be in another place than in root. > >>>> > >>>> stef > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 21, 2010

Re: [Pharo-project] Where is everyone? Watching the world cup?

by Peter Hugosson-Miller

Same here, nothing since Wednesday, so I assumed it was the football :-p Still now it's working again for me, so whatever the real problem was, it appears to have been fixed. -- Cheers, Peter

June 21, 2010

Re: [Pharo-project] OBSystemBrowser and class comments

by Lukas Renggli

I don't see this lag. Do you have a particularly long comment? Another problem could be the an old version of OB-Refactoring that provide some typing information in the comment if nothing else is there. Lukas On Friday, June 18, 2010, Adrien BARREAU <abarreau.dev(a)live.fr> wrote: > > > > > > Hello all, > > I'm writing some class comment for Citezen. > But I think something is strange: when I type something on my keyboard, there are 1 or 2 secondes of latent period before it display it on the screen. > > I don't know if it has already been signaled. > > Adrien. > > Vous voulez protÃ©ger votre vie privÃ©e ? La solution avec Internet Explorer 8Â <http://clk.atdmt.com/FRM/go/232102477/direct/01/> > -- Lukas Renggli www.lukas-renggli.ch

June 21, 2010

Re: [Pharo-project] OpenDBX for dbase files

by Benoit St-Jean

Hi Facundo, Looking at my notes : 1) Load FFI ScriptLoader loadFFI 2) Load ODBC from SqueakSource.com MCHttpRepository location: 'http://www.squeaksource.com/ODBC' user: '' password: '' 3) Initialize some stuff ExternalStructure allSubclassesDo: [:each | each compileFields]. Hope this helps. Let me know if this works... ----------------- Benoit St-Jean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) Date: Thu, 17 Jun 2010 12:21:56 -0300 From: facundov79(a)gmail.com To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] OpenDBX for dbase files Beniot,do you use this for OBDC on Pharo, http://www.squeaksource.com/@N-vIVE5EmBTpAjWY/bYzXEKgO ? Last night, I tried it but i had my image blocked. Tonight, i'll try it again. Thanks,Facundo 2010/6/17 Benoit St-Jean <bstjean(a)hotmail.ca> Hi Facundo, You can use ODBC to access it. >From what I read on the SqueakDBX web page, they don't support xBase files nor ODBC (only ODBC for POstgreSQL is listed) yet. The xBase package on squeaksource might work but your best bet would be ODBC as far as I know. ODBC works fine and is rock-solid in Pharo. I'm using it to connect to PostGreSQL, InterBase, MySQL, Oracle, DB2 and SQL Server without any problem. Hope this helps. ----------------- Benoit St-Jean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) Date: Fri, 11 Jun 2010 08:18:14 -0300 From: facundov79(a)gmail.com To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] OpenDBX for dbase files Hi at all,can I used openDBX for read dbase (.dbf) files or I need try with xbase ? regards, Facu Turn down-time into play-time with Messenger games Play Now! _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Facundo Vozzi InfOil S.A. Project Leader (+54-11) 4542-9999 x108 fvozzi(a)infoil.com.ar _________________________________________________________________ Turn down-time into play-time with Messenger games http://go.microsoft.com/?linkid=9734385

June 21, 2010

Re: [Pharo-project] [Vm-dev] Re: [squeak-dev] Teleplace Cog VMs are now available

by Andreas Raab

On 6/20/2010 2:23 PM, Lukas Renggli wrote: > > Thank you Eliot. > > This is wonderful, it feels like I just got a new laptop :-) > > I noticed some problems in the continuation tests of Seaside > (WAContinuationTest, WAFlowPlatformTest and > WAPartialContinuationTest): > > "Computation has been terminated" in MethodContext>>cannotReturn: > > Is this a known problem? Or is this maybe specific to Pharo on Cog? It's a Cog bug. GeneratorTest dies with the same symptoms in 4.1. Cheers, - Andreas > On 20 June 2010 22:53, stephane ducasse<stephane.ducasse(a)gmail.com> wrote: >> This is really an excellent news. I open a lot of new futures! >> Thanks teleplace, andreas and all the people that helped. >> >> Stef >> PS: you already answer my questions about platform were the jit cannot work so this is great. >> >> >> On Jun 20, 2010, at 10:11 PM, Eliot Miranda wrote: >> >>> Hi All, >>> >>> it gives me great pleasure to announce that the Teleplace Cog VMs are now available. Huge thanks to all at Teleplace who have given me the opportunity to build Cog and release it as open source, been willing guinea pigs braving its bugs, and providing indispensable participation in getting Cog to its current state. Huge thanks are also due to the original Back To The Future team whose VMMaker Cog extends to write the VM, and to Peter Deutsch from whom I've taken many ideas. >>> >>> This release contains two VMs. The Stack VM, is a cross-platform interpreter that uses context-to-stack mapping to achieve modest performance gains. The Cog VM is a just-in-time compiler that currently supports only x86 that builds upon the Stack VM to achieve substantial performance improvements. The release is in the form of a Monticello package containing the VMMaker source and a tarball containing the platform sources, the generated sources and a Squeak 4.1 image containing the VMMaker sources. Download both at >>> http://ftp.squeak.org/Cog/VMMaker-oscog.11.mcz >>> http://ftp.squeak.org/Cog/OpenSourceCog.tar.gz >>> >>> Cog VMs: >>> >>> The Cog VMs are Squeak/Croquet VMs that run closure Squeak/Croquet/Pharo/Cuis images. The VMs support existing plugin source but will require plugins to be recompiled as the VM_PROXY_MAJOR plugin api has been extended. >>> >>> This release contains two distinct VMs, the StackInterpreter and the Cogit. The StackInterpreter is a fully-portable plug-in replacement for the current closure Squeak VMs and images. The Stack VM uses context-to-stack mapping and a somewhat improved garbage collector to achieve modest but useful performance gains in the 10% to 15% range. The StackInterpreter is intended to supersede the Squeak VM on platforms where the Cogit cannot be used. The Cogit extends the StackInterpreter with a just-in-time compiler that uses aggressive inline caching techniques to deliver substantial performance gains in the 3x to 15x range, depending on benchmark. The Cogit currently supports only x86 and the floating-point primitives and parts of the platform support code depend on SSE2. I hope members of the community will attempt to port it, e.g. to ARM, PowerPC and x86-64. The Cogit (excuse the pun) is so named because it is both an interpreter and a JIT, choosing not to generate ma chine code for large methods, interpreting them instead, the default policy being not to JIT methods with more than 60 literals. >>> >>> The Cog VM requires a few minor image changes all in image/NecessaryImageChangesForCogToWork.1.cs. The JIT's machine-code SmallInteger primitives insist on a SmallInteger receiver so the primitives in LargePositiveInteger = ~= bitAnd: bitOr: butShift: and bitXor: cannot be used and these methods must be deleted. The Cogit inlines the address of the Character instance table, Smalltalk specialObjectsArray at: 25, into the machine-code at: primitive for faster ByteString>>at: and so the table cannot be rebuilt in SmalltalkImage>>recreateSpecialObjectsArray. The new version preserves the existing table. Both VMs maintain floats in platform order to ease implementation of machine code floating-point primitives, and hence internally are in little-endian order instead of big-endian in current Squeak images. While the VMs convert float order automatically on load they do require special accessing primitives Float>>basicAt:& Float>>basicAt:put: that undo the reversal and an swer Float contents in big-endian order so that e.g. Float>>hash is unchanged. The methods assume these primitives can fail, allowing the code to be used on current Squeak VMs. >>> >>> The image/VMMaker-Squeak4.1.image is a Squeak 4.1 image, runnable with the current Squeak VMs, that contains these changes, and can hence also be run with a Cog VM. But beware, once an image has been saved on Cog it cannot be run by an existing Squeak VM, because existing VMs cannot undo the Float order change. >>> >>> >>> Platform Subsystem: >>> >>> Most of the platform subsystem is unchanged but there are some important changes that need description. The biggest change is the heartbeat and the clock in platforms/unix/vm/sqUnixHeartbeat.c and platforms/win32/vm/sqWin32Heartbeat.c. The Cog VMs avoid the slow and variable interruptCheckCounter, folding the event check into the stack overflow check on frame build. The heartbeat, typically 500Hz or 1KHz, changes the stackLimit to a value that will always fail. On the next frame building send the VM will enter stack overflow handling that, as a side effect, will also check for events. This is more efficient than the update of interruptCheckCounter and much more regular. If one is running code that executes long-running primitives (e.g. large integer arithmetic) the counter approach will result in too low an interrupt check frequency, and conversely if one is running normal code the interrupt check frequency can be very high. >>> >>> The heartbeat also maintains a 64-bit microsecond clock, UTC microseconds from 1901, from which the backward-compatible millisecond and second clocks are derived. Primitives exist to answer UTC microseconds and local microseconds. Updating the clock in the heartbeat results in a 1 or 2 millisecond resolution but avoids the cost of accessing the OS time on every prim tie which we've found important for performance at Teleplace. The 64-bit microsecond clocks provide a unified time basis and eliminate wrapping (for the next 54,000 years at least). I hope community images will move to these clocks. It's worked well in VisualWorks. >>> >>> Another significant change is in the external semaphore table support code. This is now lock-free at the cost of having to specify a maximum number of external semaphores at start-up (default 256). The support code for the lock-free data structures are processor-specific and is currently implemented only for x86 and gcc-compatible compilers; see platforms/Cross/vm/{sqAtomicOps.h,sqMemoryFence.h}. >>> >>> There is also improved crash reporting code that prints a primitive log and a C backtrace in addition to the Smalltalk backtrace. See platforms/Mac OS/vm/sqMacMain.c, platforms/unix/vm/sqUnixMain.c, platforms/win32/vm/sqWin32Intel.c& platforms/win32/vm/sqWin32Backtrace.c. >>> >>> Finally there is support for the QVMProfiler, a pc-sampling profiler for profiling at the VM level. See platforms/unix/vm/sqUnixVMProfile.c and platforms/win32/vm/sqWin32VMProfile.c. The profiler itself is in the VMMaker image described below in Qwaq-VMProfiling. >>> >>> There are also changes to do with Teleplace-specific extensions to the HostWindowPlugin but these are not essential to Cog. >>> >>> >>> VMMaker and Slang: >>> >>> The image/VMMaker-Squeak4.1.image Squeak 4.1 image contains the complete Cog VMMaker with necessary support code for simulation. This image was used to generate the sources in the src and stacksrc directories. >>> >>> Cog's VMMaker is substantially revised and extended from the current VMMaker. It supports multiple classes, not just Interpreter and superclasses, because both context-to-stack mapping and the Cogit are too complex to write monolithically. Classes can specify ancilliaryClasses and ancilliaryStructClasses, such as CoInterpreterStackPage, CogMethod and CogAbstractInstruction. The Monticello package version is included in the header of all generated files and constitutes the version stamp for generated code. Code is generated in sorted order so that minor changes in the Smalltalk source produce correspondingly minor changes in the generated code. The gnuification step is built-in to VMMaker. No effort has been made to maintain 64-bit compatibility. Apologies, this was unaffordable. >>> >>> The VMMaker generates a single source tree used by all platforms. Instead of deciding at generation time whether to use the Interpreter struct the generated code depends on the SQ_USE_GLOBAL_STRUCT define which can be overridden in platform makefiles. All plugins live in src/plugins and platform makefiles along with plugins.int and plugins.ext files in the build subdirectories decide which plugins are built as external or internal. The VM Generation Workspace from Workspace.text workspace contains dots to generate the sources. We no longer use the VMMakerTool since there should be nothing platform-specific in the generated sources (if we add ports to other ISAs all their source can be included and selected as required by the platform makefiles). >>> >>> Since the Cogit generates x86 machine code simulation is much more complex. There is a support plugin, platforms/Cross/plugins/BochsIA32Plugin that depends on a large simulation of the x86 family implemented in C++ (see processors/IA32/bochs) and on Alien. I use the simulator frequently (but note that I haven't had time to build a working version for Squeak 4.1). I have tested Cog simulation in this image, running on the image/VMMaker-Squeak4.1.image itself. The VM Simulation Workspace in the VMMaker image contains an example doit that starts the simulator. Be patient, even on a fast machine unhibernating the Squeak display background image takes nearly a minute. Native fonts do not (yet) simulate correctly, but the system runs. But note that I have only attempted to build and run the simulator on Mac OS X. I expect Bochs can be built on linux and win32 but I have not tried. By the way, I've not described how to run the Bochs simulator on the current Squeak VM. That's because the plugin depends on the heartbeat to break out of simulation occasionally via a new interpreterProxy entry point setInterruptCheckChain. As this isn't supported by the current Squeak VMs the plugin would require modification. So to simulate first build either of the Cog VMs and then run the simulation with it. >>> >>> There are a number of unpublished changes to the base other than those in NecessaryImageChangesForCogToWork.1.cs. This is partly laziness on my part, partly avoiding publishing things in advance of Cog. These changes are better motivated once Cog is in use. There are changes to the "translated primitives" (see implementors of translatedPrimitives) which replace messages with method tags for generation directives. The Cog VMMaker uses Object>>perform:with:with:with:with:& Object>>perform:with:with:with:with:with: during simulation, and Collection>>#fold:& SquenceableCollection>>#copyUpThrough: during generation. Object>>inline: and Object var:declareC:, which are mispackaged in Kernel in Squeak 4.1 are obsolete (method tags being used instead) and have been removed. I have changed Integer>>hex and Integer>>hex8 back to their original semantics as of 3.8. Backward compatibility is important and one can easily add new selectors if one wants different functionality. VMMaker was here first ;) >>> >>> >>> Tarball: >>> >>> The top-level directories in the tarball are >>> >>> src >>> the tree for the Cog generated sources including all plugins >>> stacksrc/vm >>> the directory containing the Stack VM source (plugins can be taken from above) >>> platforms >>> the usual svn platform tree but including Cog specific changes such as the heartbeat >>> processors >>> the tree containing simulation support code, i.e. the bochs C++ x86 simulation library, along with a potential ARM, PowerPC& MIPS simulator, Skeye. >>> >>> image >>> the Cog-prepared Squeak 4.1 VMMaker image >>> scripts >>> some svn scripts to revert unchanged plugins that haven't really changed >>> >>> cygwinbuild >>> the win32 build directory >>> winbuild >>> the old win32 build directory for minnow gcc 2.95. Not entirely obsolete as the cygwin build as yet fails to generate a functional FFIPlugin >>> macbuild >>> the CoreVM.xcodeproj and support build projects for Mac OS X 10.5 or better >>> unixbuild >>> the build directory for linux >>> >>> >>> Building Cog: >>> >>> Each build directory above contains a HowToBuild file that describes building in more detail. The build directories only contain Cogit makefiles. f you want to build a Stack VM you're on your own but this is very close to the existing Squeak VM build. >>> >>> >>> Status: >>> The Cogit VM has been our sole VM at Teleplace for nearly a year. We do occasionally find bugs and there are almost certainly areas of functionality that we have not touched (for example I know that co-routining does not yet work). If you find a bug please try and create a reproducible test case and let me know. I can't promise to take a look or fix it but I am motivated to do so and will try my best as time allows. Better still if you find and fix bugs be sure to let me know. >>> >>> License (MIT): >>> All contributions from Teleplace in this release are >>> Copyright (c) 2010 Teleplace, Inc. >>> >>> Permission is hereby granted, free of charge, to any person obtaining a copy >>> of this software and associated documentation files (the "Software"), to deal >>> in the Software without restriction, including without limitation the rights >>> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell >>> copies of the Software, and to permit persons to whom the Software is >>> furnished to do so, subject to the following conditions: >>> >>> The above copyright notice and this permission notice shall be included in >>> all copies or substantial portions of the Software. >>> >>> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR >>> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, >>> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE >>> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER >>> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, >>> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN >>> THE SOFTWARE. >>> >>> Eliot Miranda >>> June 2010 >>> >>> >> >> >> > > >

June 20, 2010

Re: [Pharo-project] [squeak-dev] Teleplace Cog VMs are now available

by Eliot Miranda

On Sun, Jun 20, 2010 at 2:23 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Thank you Eliot. > > This is wonderful, it feels like I just got a new laptop :-) > :) > I noticed some problems in the continuation tests of Seaside > (WAContinuationTest, WAFlowPlatformTest and > WAPartialContinuationTest): > > "Computation has been terminated" in MethodContext>>cannotReturn: > > Is this a known problem? Or is this maybe specific to Pharo on Cog? > This is a known area of problems. From my announcement: Status: The Cogit VM has been our sole VM at Teleplace for nearly a year. We do occasionally find bugs and there are almost certainly areas of functionality that we have not touched (*for example I know that co-routining does not yet work*). If you find a bug please try and create a reproducible test case and let me know. I can't promise to take a look or fix it but I am motivated to do so and will try my best as time allows. Better still if you find and fix bugs be sure to let me know. The use of context-to-stack mapping is fundamental to the performance improvements in Cog and it *should* be transparent, but so far I've only fixed what issues we've encountered in our usage at Teleplace. I expect the next few weeks to involve some bug fixing as it is used in a much broader context (no pun intended). Y'all can help by giving me reproducible test cases. This can be in the form of a precise specification of an image configuration and a doit, but even easier is to save an image that exhibits the crash on start-up. e.g. Smalltalk saveAs: 'crash.image' thenQuit: true. MyClass crashTheVM I also need to write the sequence of blog posts on the JIT I've been meaning to write for over a year now, as others will want to understand and, I hope, port Cog to other processors. There's also the need to improve performance. Right now the code generator is a very naive JIT where every there is no inter-bytecode optimization and hence every push or pop in the bytecode is reflected in a real push or pop in the native code. This makes loops such as 1 to: n do: [:i|... ] very slow because the send: #<= (1 arg); jumpFalseTo: L2 in the underlying code actually runs a non-inlined SmallInteger <= primitive which pushes the actual true object, which the jump bytecode must compare against the actual true false object. In the VisualWorks code generator the JIT spits out two paths here, one that tests or SmallIntegers and then does the comparison and jump directly branching on the condition codes. Consequently loops in VsualWorks are much faster. Also, the object representation is convoluted, compact classes being OK for reducing space overhead but bad at creating overhead and complexity, so much so that Cog as yet lacks machine code primitives for instance creation and at:put:. So I hope that soon we'll upgrade the code generator and the object representation and will see another significant jump in compute performance to bring us up to VisualWorks levels. I hope that we'll also start working on inlining and get the fastest Smalltalk VM ever. We have a really exciting opportunity here with Exupery and Igor's Native Boost to do inlining in a Klein-like way, i.e. having SMalltalk code do inlining and code optimization. The only concern here is portability; keeping an intermediate bytecode might be wise. But we'll see. I'm also going to be working on the FFI, in part with my GSoC student, but also in Teleplace where I have threaded/non-blocking/overlapped calls woking in prototype form, but as yet lack proper calbacks. So that speculation aside please do prepare reproducible cases of crashes or differences in behaviour between the current VM and Cog (I've just remembered that another difference is that Cog will produce Float infinity for 1.0/0.0 instead of failing). Crashes need to be fixed. Some semantic issues may need to change (for example I think the floating-point behaviour is better, does this need a flag to control as in VisualWorks's case, etc). But Cog being available is only the beginning, and now we can all be involved. cheers Eliot

June 20, 2010

Re: [Pharo-project] [squeak-dev] Teleplace Cog VMs are now available

by Andreas Raab

On 6/20/2010 2:42 PM, Rob Rothwell wrote: > For the binary-challenged, I am sure some kind soul will post compiled > versions somewhere...! For Windows, get yours here: http://squeakvm.org/win32/experimental/CogSqueak4.1.zip Cheers, - Andreas > (I ALWAYS struggle with build.bat, missing files, environment variables, > and the like...) > > Take care, > > Rob > > On Sun, Jun 20, 2010 at 5:37 PM, John M McIntosh > <johnmci(a)smalltalkconsulting.com > <mailto:johnmci@smalltalkconsulting.com>> wrote: > > > Wonderful news. > > > On 2010-06-20, at 1:11 PM, Eliot Miranda wrote: > >> The Cogit currently supports only x86 and the floating-point >> primitives and parts of the platform support code depend on SSE2. >> I hope members of the community will attempt to port it, e.g. to >> ARM, PowerPC and x86-64. > > Now before anyone asks, it's very doubtful you will see Cogit on the > iOS series of operating systems (iphone/ipad). I have had detailed > discussions with the Apple Security team since their goal is to > prevent user level code from doing dynamic code generation. > > mmap for example won't return a page of memory that is executable. > > Let's say the probability of getting Apple to change their minds on > this is zero. > > However I'll look into the StackInterpreter for the Macintosh 5.x VM > and the iOS flavour, mind if anyone wants to do that chore early > then they should ping me. > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com > <mailto:johnmci@smalltalkconsulting.com>> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > >

June 20, 2010

Re: [Pharo-project] [Vm-dev] Re: [squeak-dev] Teleplace Cog VMs are now available

by Rob Rothwell

For the binary-challenged, I am sure some kind soul will post compiled versions somewhere...! (I ALWAYS struggle with build.bat, missing files, environment variables, and the like...) Take care, Rob On Sun, Jun 20, 2010 at 5:37 PM, John M McIntosh < johnmci(a)smalltalkconsulting.com> wrote: > > Wonderful news. > > > On 2010-06-20, at 1:11 PM, Eliot Miranda wrote: > > The Cogit currently supports only x86 and the floating-point primitives > and parts of the platform support code depend on SSE2. I hope members of > the community will attempt to port it, e.g. to ARM, PowerPC and x86-64. > > > Now before anyone asks, it's very doubtful you will see Cogit on the iOS > series of operating systems (iphone/ipad). I have had detailed discussions > with the Apple Security team since their goal is to prevent user level code > from doing dynamic code generation. > > mmap for example won't return a page of memory that is executable. > > Let's say the probability of getting Apple to change their minds on this is > zero. > > However I'll look into the StackInterpreter for the Macintosh 5.x VM and > the iOS flavour, mind if anyone wants to do that chore early then they > should ping me. > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > >

June 20, 2010

Re: [Pharo-project] [squeak-dev] Teleplace Cog VMs are now available

by John M McIntosh

Wonderful news. On 2010-06-20, at 1:11 PM, Eliot Miranda wrote: > The Cogit currently supports only x86 and the floating-point primitives and parts of the platform support code depend on SSE2. I hope members of the community will attempt to port it, e.g. to ARM, PowerPC and x86-64. Now before anyone asks, it's very doubtful you will see Cogit on the iOS series of operating systems (iphone/ipad). I have had detailed discussions with the Apple Security team since their goal is to prevent user level code from doing dynamic code generation. mmap for example won't return a page of memory that is executable. Let's say the probability of getting Apple to change their minds on this is zero. However I'll look into the StackInterpreter for the Macintosh 5.x VM and the iOS flavour, mind if anyone wants to do that chore early then they should ping me. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

June 20, 2010

Re: [Pharo-project] [squeak-dev] Teleplace Cog VMs are now available

by Lukas Renggli

Thank you Eliot. This is wonderful, it feels like I just got a new laptop :-) I noticed some problems in the continuation tests of Seaside (WAContinuationTest, WAFlowPlatformTest and WAPartialContinuationTest): "Computation has been terminated" in MethodContext>>cannotReturn: Is this a known problem? Or is this maybe specific to Pharo on Cog? Cheers, Lukas On 20 June 2010 22:53, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: > This is really an excellent news. I open a lot of new futures! > Thanks teleplace, andreas and all the people that helped. > > Stef > PS: you already answer my questions about platform were the jit cannot work so this is great. > > > On Jun 20, 2010, at 10:11 PM, Eliot Miranda wrote: > >> Hi All, >> >> Â Â Â it gives me great pleasure to announce that the Teleplace Cog VMs are now available. Â Huge thanks to all at Teleplace who have given me the opportunity to build Cog and release it as open source, been willing guinea pigs braving its bugs, and providing indispensable participation in getting Cog to its current state. Â Huge thanks are also due to the original Back To The Future team whose VMMaker Cog extends to write the VM, and to Peter Deutsch from whom I've taken many ideas. >> >> This release contains two VMs. Â The Stack VM, is a cross-platform interpreter that uses context-to-stack mapping to achieve modest performance gains. Â The Cog VM is a just-in-time compiler that currently supports only x86 that builds upon the Stack VM to achieve substantial performance improvements. Â The release is in the form of a Monticello package containing the VMMaker source and a tarball containing the platform sources, the generated sources and a Squeak 4.1 image containing the VMMaker sources. Â Download both at >> Â Â Â http://ftp.squeak.org/Cog/VMMaker-oscog.11.mcz >> Â Â Â http://ftp.squeak.org/Cog/OpenSourceCog.tar.gz >> >> Cog VMs: >> >> The Cog VMs are Squeak/Croquet VMs that run closure Squeak/Croquet/Pharo/Cuis images. The VMs support existing plugin source but will require plugins to be recompiled as the VM_PROXY_MAJOR plugin api has been extended. >> >> This release contains two distinct VMs, the StackInterpreter and the Cogit. Â The StackInterpreter is a fully-portable plug-in replacement for the current closure Squeak VMs and images. Â The Stack VM uses context-to-stack mapping and a somewhat improved garbage collector to achieve modest but useful performance gains in the 10% to 15% range. Â The StackInterpreter is intended to supersede the Squeak VM on platforms where the Cogit cannot be used. Â The Cogit extends the StackInterpreter with a just-in-time compiler that uses aggressive inline caching techniques to deliver substantial performance gains in the 3x to 15x range, depending on benchmark. Â The Cogit currently supports only x86 and the floating-point primitives and parts of the platform support code depend on SSE2. Â I hope members of the community will attempt to port it, e.g. to ARM, PowerPC and x86-64. Â The Cogit (excuse the pun) is so named because it is both an interpreter and a JIT, choosing not to generate machine code for large methods, interpreting them instead, the default policy being not to JIT methods with more than 60 literals. >> >> The Cog VM requires a few minor image changes all in image/NecessaryImageChangesForCogToWork.1.cs. Â The JIT's machine-code SmallInteger primitives insist on a SmallInteger receiver so the primitives in LargePositiveInteger = ~= bitAnd: bitOr: butShift: and bitXor: cannot be used and these methods must be deleted. Â The Cogit inlines the address of the Character instance table, Smalltalk specialObjectsArray at: 25, into the machine-code at: primitive for faster ByteString>>at: and so the table cannot be rebuilt in SmalltalkImage>>recreateSpecialObjectsArray. Â The new version preserves the existing table. Â Both VMs maintain floats in platform order to ease implementation of machine code floating-point primitives, and hence internally are in little-endian order instead of big-endian in current Squeak images. Â While the VMs convert float order automatically on load they do require special accessing primitives Float>>basicAt: & Float>>basicAt:put: that undo the reversal and answer Float contents in big-endian order so that e.g. Float>>hash is unchanged. Â The methods assume these primitives can fail, allowing the code to be used on current Squeak VMs. >> >> The image/VMMaker-Squeak4.1.image is a Squeak 4.1 image, runnable with the current Squeak VMs, that contains these changes, and can hence also be run with a Cog VM. Â But beware, once an image has been saved on Cog it cannot be run by an existing Squeak VM, because existing VMs cannot undo the Float order change. >> >> >> Platform Subsystem: >> >> Most of the platform subsystem is unchanged but there are some important changes that need description. Â The biggest change is the heartbeat and the clock in platforms/unix/vm/sqUnixHeartbeat.c and platforms/win32/vm/sqWin32Heartbeat.c. Â The Cog VMs avoid the slow and variable interruptCheckCounter, folding the event check into the stack overflow check on frame build. Â The heartbeat, typically 500Hz or 1KHz, changes the stackLimit to a value that will always fail. Â On the next frame building send the VM will enter stack overflow handling that, as a side effect, will also check for events. Â This is more efficient than the update of interruptCheckCounter and much more regular. Â If one is running code that executes long-running primitives (e.g. large integer arithmetic) the counter approach will result in too low an interrupt check frequency, and conversely if one is running normal code the interrupt check frequency can be very high. >> >> The heartbeat also maintains a 64-bit microsecond clock, UTC microseconds from 1901, from which the backward-compatible millisecond and second clocks are derived. Â Primitives exist to answer UTC microseconds and local microseconds. Â Updating the clock in the heartbeat results in a 1 or 2 millisecond resolution but avoids the cost of accessing the OS time on every prim tie which we've found important for performance at Teleplace. Â The 64-bit microsecond clocks provide a unified time basis and eliminate wrapping (for the next 54,000 years at least). Â I hope community images will move to these clocks. Â It's worked well in VisualWorks. >> >> Another significant change is in the external semaphore table support code. Â This is now lock-free at the cost of having to specify a maximum number of external semaphores at start-up (default 256). Â The support code for the lock-free data structures are processor-specific and is currently implemented only for x86 and gcc-compatible compilers; see platforms/Cross/vm/{sqAtomicOps.h,sqMemoryFence.h}. >> >> There is also improved crash reporting code that prints a primitive log and a C backtrace in addition to the Smalltalk backtrace. Â See platforms/Mac OS/vm/sqMacMain.c, platforms/unix/vm/sqUnixMain.c, platforms/win32/vm/sqWin32Intel.c & platforms/win32/vm/sqWin32Backtrace.c. >> >> Finally there is support for the QVMProfiler, a pc-sampling profiler for profiling at the VM level. Â See platforms/unix/vm/sqUnixVMProfile.c and platforms/win32/vm/sqWin32VMProfile.c. Â The profiler itself is in the VMMaker image described below in Qwaq-VMProfiling. >> >> There are also changes to do with Teleplace-specific extensions to the HostWindowPlugin but these are not essential to Cog. >> >> >> VMMaker and Slang: >> >> The image/VMMaker-Squeak4.1.image Squeak 4.1 image contains the complete Cog VMMaker with necessary support code for simulation. This image was used to generate the sources in the src and stacksrc directories. >> >> Cog's VMMaker is substantially revised and extended from the current VMMaker. Â It supports multiple classes, not just Interpreter and superclasses, because both context-to-stack mapping and the Cogit are too complex to write monolithically. Â Classes can specify ancilliaryClasses and ancilliaryStructClasses, such as CoInterpreterStackPage, CogMethod and CogAbstractInstruction. Â The Monticello package version is included in the header of all generated files and constitutes the version stamp for generated code. Â Code is generated in sorted order so that minor changes in the Smalltalk source produce correspondingly minor changes in the generated code. Â The gnuification step is built-in to VMMaker. Â No effort has been made to maintain 64-bit compatibility. Â Apologies, this was unaffordable. >> >> The VMMaker generates a single source tree used by all platforms. Â Instead of deciding at generation time whether to use the Interpreter struct the generated code depends on the SQ_USE_GLOBAL_STRUCT define which can be overridden in platform makefiles. Â All plugins live in src/plugins and platform makefiles along with plugins.int and plugins.ext files in the build subdirectories decide which plugins are built as external or internal. Â The VM Generation Workspace from Workspace.text workspace contains dots to generate the sources. Â We no longer use the VMMakerTool since there should be nothing platform-specific in the generated sources (if we add ports to other ISAs all their source can be included and selected as required by the platform makefiles). >> >> Since the Cogit generates x86 machine code simulation is much more complex. Â There is a support plugin, platforms/Cross/plugins/BochsIA32Plugin that depends on a large simulation of the x86 family implemented in C++ (see Â processors/IA32/bochs) and on Alien. Â I use the simulator frequently (but note that I haven't had time to build a working version for Squeak 4.1). Â I have tested Cog simulation in this image, running on the image/VMMaker-Squeak4.1.image itself. Â The VM Simulation Workspace in the VMMaker image contains an example doit that starts the simulator. Be patient, even on a fast machine unhibernating the Squeak display background image takes nearly a minute. Â Native fonts do not (yet) simulate correctly, but the system runs. Â But note that I have only attempted to build and run the simulator on Mac OS X. Â I expect Bochs can be built on linux and win32 but I have not tried. Â By the way, I've not described how to run the Bochs simulator on the current Squeak VM. Â That's because the plugin depends on the heartbeat to break out of simulation occasionally via a new interpreterProxy entry point setInterruptCheckChain. Â As this isn't supported by the current Squeak VMs the plugin would require modification. Â So to simulate first build either of the Cog VMs and then run the simulation with it. >> >> There are a number of unpublished changes to the base other than those in NecessaryImageChangesForCogToWork.1.cs. Â This is partly laziness on my part, partly avoiding publishing things in advance of Cog. Â These changes are better motivated once Cog is in use. Â There are changes to the "translated primitives" (see implementors of translatedPrimitives) which replace messages with method tags for generation directives. Â The Cog VMMaker uses Object>>perform:with:with:with:with: & Object>>perform:with:with:with:with:with: during simulation, and Collection>>#fold: & SquenceableCollection>>#copyUpThrough: during generation. Â Object>>inline: and Object var:declareC:, which are mispackaged in Kernel in Squeak 4.1 are obsolete (method tags being used instead) and have been removed. I have changed Integer>>hex and Integer>>hex8 back to their original semantics as of 3.8. Â Backward compatibility is important and one can easily add new selectors if one wants different functionality. Â VMMaker was here first ;) >> >> >> Tarball: >> >> The top-level directories in the tarball are >> >> Â Â Â src >> Â Â Â Â Â Â Â the tree for the Cog generated sources including all plugins >> Â Â Â stacksrc/vm >> Â Â Â Â Â Â Â the directory containing the Stack VM source (plugins can be taken from above) >> Â Â Â platforms >> Â Â Â Â Â Â Â the usual svn platform tree but including Cog specific changes such as the heartbeat >> Â Â Â processors >> Â Â Â Â Â Â Â the tree containing simulation support code, i.e. the bochs C++ x86 simulation library, along with a potential ARM, PowerPC & MIPS simulator, Skeye. >> >> Â Â Â image >> Â Â Â Â Â Â Â the Cog-prepared Squeak 4.1 VMMaker image >> Â Â Â scripts >> Â Â Â Â Â Â Â some svn scripts to revert unchanged plugins that haven't really changed >> >> Â Â Â cygwinbuild >> Â Â Â Â Â Â Â the win32 build directory >> Â Â Â winbuild >> Â Â Â Â Â Â Â the old win32 build directory for minnow gcc 2.95. Â Not entirely obsolete as the cygwin build as yet fails to generate a functional FFIPlugin >> Â Â Â macbuild >> Â Â Â Â Â Â Â the CoreVM.xcodeproj and support build projects for Mac OS X 10.5 or better >> Â Â Â unixbuild >> Â Â Â Â Â Â Â the build directory for linux >> >> >> Building Cog: >> >> Each build directory above contains a HowToBuild file that describes building in more detail. Â The build directories only contain Cogit makefiles. Â f you want to build a Stack VM you're on your own but this is very close to the existing Squeak VM build. >> >> >> Status: >> The Cogit VM has been our sole VM at Teleplace for nearly a year. Â We do occasionally find bugs and there are almost certainly areas of functionality that we have not touched (for example I know that co-routining does not yet work). Â If you find a bug please try and create a reproducible test case and let me know. Â I can't promise to take a look or fix it but I am motivated to do so and will try my best as time allows. Â Better still if you find and fix bugs be sure to let me know. >> >> License (MIT): >> All contributions from Teleplace in this release are >> Copyright (c) 2010 Teleplace, Inc. >> >> Permission is hereby granted, free of charge, to any person obtaining a copy >> of this software and associated documentation files (the "Software"), to deal >> in the Software without restriction, including without limitation the rights >> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell >> copies of the Software, and to permit persons to whom the Software is >> furnished to do so, subject to the following conditions: >> >> The above copyright notice and this permission notice shall be included in >> all copies or substantial portions of the Software. >> >> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR >> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, >> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE >> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER >> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, >> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN >> THE SOFTWARE. >> >> Eliot Miranda >> June 2010 >> >> > > > -- Lukas Renggli www.lukas-renggli.ch

June 20, 2010