February 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 22586d: 40500

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 22586ded523603b7502e4b5b68772f23fff1fae9 https://github.com/pharo-project/pharo-core/commit/22586ded523603b7502e4b5b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-23 (Mon, 23 Feb 2015) Changed paths: R Komitter.package/extension/EclipseUIThemeIcons/instance/overlayAddIconContents.st R Komitter.package/extension/EclipseUIThemeIcons/instance/overlayModificationIconContents.st R Komitter.package/extension/EclipseUIThemeIcons/instance/overlayRemoveIconContents.st A Komitter.package/extension/ThemeIcons/instance/overlayAddIconContents.st A Komitter.package/extension/ThemeIcons/instance/overlayModificationIconContents.st A Komitter.package/extension/ThemeIcons/instance/overlayRemoveIconContents.st M NativeBoost-Win32.package/NBWin32Window.class/class/as yet unclassified/createWindowExA_lpClassName_lpWindowName_dwStyle_x_y_width_height_hWndParent_hMenu_hInstance_lParam_.st M NativeBoost-Win32.package/NBWin32Window.class/class/as yet unclassified/createWindowExW_lpClassName_lpWindowName_dwStyle_x_y_width_height_hWndParent_hMenu_hInstance_lParam_.st M NativeBoost-Win32.package/NativeBoostWin32.class/class/library loading/getModuleHandle_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script500.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40500.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClass.class/instance/initialize-release/obsolete.st M Traits.package/TClass.class/instance/testing/isObsolete.st Log Message: ----------- 40500 14631 DNU GLMThemeIcons >> overlayModificationIconContents https://pharo.fogbugz.com/f/cases/14631 14941 isObsolete returns true for anonymous classes https://pharo.fogbugz.com/f/cases/14941 14728 NBFFICalloutAPI option WinUnicode is not prefixed with opt, as all the other options https://pharo.fogbugz.com/f/cases/14728 http://files.pharo.org/image/40/40500.zip

Feb. 23, 2015

Re: [Pharo-dev] Determine if a method is Jitted or not

by Eliot Miranda

On Feb 23, 2015, at 7:50 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2015-02-23 16:36 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> Hi Thierry, >> >> there's an unadvertised primitive called Context>>#xRay (or ContextPart>>#xRay) that answers these questions for tests. I'm away from the system right now but I'll get you the source soon. Also, the limit on jutting methods, 60 literals, is a default. There's a command line option -maxcoglits (IIRC) that you can change. > > Thanks Eliot! > > It's helping a lot to guide me, even if I have to work at the ast level and, as a result, I estimate the number of literals in the bytecode by counting the number of literal nodes in the AST, with the approximation that ~100 literal nodes will make it under the limit. > > Making it under the limit shaves 30% of the execution time of a parse with SmaCC. And it avoids the too long methods as a side benefit. > > I would dream of having precise ways of estimating things like that on the AST. It's interesting to hit those "I'd like to be able to predict the performance of that piece of code" issues. Alas two things other than the AST affect the number of literals. First is the specialSelectors; these are used for sends only. So if a method only sends one of the special selectors the selector will not occur in the method as a literal. Second is the bytecode set. While we only have one set now, Sista is introducing another, and Newspeak has its own. In the current set, -1, 0, 1 & 2 and true and false have bytecodes to push these literals, so they don't occur as literals in methods. In both the Sista and the Newspeak sets there are bytecodes that encode a much wider range of integers and characters as bytecodes (a push literal bytecode takes 1 byte for the bytecode and 4 or 8 bytes for the literal; a bytecode for the 16-bit integer range takes 3 bytes). Another thing that affects the number of literals is the compiler's decision to include selectors for optimized methods such as ifTrue: et al (which I think is a very good thing). If you could ask the back end which literal would be encoded as a literal (and if course the question is asked when bytecode is generated) you could get a more accurate count. HTH > > Thierry > >> >> Eliot (phone) >> >> On Feb 23, 2015, at 5:05 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> > Hi All, >> > >> > anybody knows how to check if a method is jitted or not? >> > >> > I remember (maybe wrongly) that the Jit in Cog has a configurable limit on the number of bytecodes for a method to be jitted or not; I'm looking into the performance of generated code where I can, more or less, control the length of methods (SmaCC) and I'd like to find the optimum point. >> > >> > Thanks, >> > >> > Thierry >

Feb. 23, 2015

Class/Method common interface idea

by Yuriy Tymchuk

Hi, so my idea is that maybe we can create traits for common classes(behaviors) and methods properties. Because besides the real ones there are ring, monticello and other definitions. It would be nice if one could browse the trait that defines common properties for all the definitions + if someone needs a custom property - there is one place to add it. Uko

Feb. 23, 2015

Re: [Pharo-dev] Fwd: Build failed in Jenkins: NeoCSV Â» 40,stable,vm #474

by Christophe Demarey

Thanks, I just cleaned the builds folder Le 23 fÃ©vr. 2015 Ã 16:27, Sven Van Caekenberghe a Ã©crit : > Disk full on the contribution CI ... > >> Begin forwarded message: >> >> Date: 23 Feb 2015 16:26:46 CET >> From: ci-pharo-contribution(a)inria.fr >> To: sven(a)stfx.eu >> Subject: Build failed in Jenkins: NeoCSV Â» 40,stable,vm #474 >> >> See <https://ci.inria.fr/pharo-contribution/job/NeoCSV/PHARO=40,VERSION=stable,V…> >> >> ------------------------------------------ >> Started by upstream project "NeoCSV" build number 475 >> originally caused by: >> Started by timer >> Building remotely on pharo-contribution-linux64.ci.inria.fr (32 64 linux) in workspace <https://ci.inria.fr/pharo-contribution/job/NeoCSV/PHARO=40,VERSION=stable,V…> >> >> Deleting project workspace... [vm] $ /bin/sh -xe /tmp/hudson5392095292005988537.sh >> + export JOB_NAME=NeoCSV >> + bash >> + wget --quiet -O - get.pharo.org/40+vm >> Downloading the latest 40 Image: >> http://files.pharo.org/image/40/latest.zip >> Pharo.image >> Downloading the latest pharoVM: >> http://files.pharo.org/vm/pharo/linux/stable.zip >> pharo-vm/pharo >> Downloading PharoV10.sources: >> http://files.pharo.org/sources//PharoV10.sources.zip >> Downloading PharoV20.sources: >> http://files.pharo.org/sources//PharoV20.sources.zip >> Downloading PharoV30.sources: >> http://files.pharo.org/sources//PharoV30.sources.zip >> pharo-vm/PharoV30.sources: write error (disk full?). Continue? (y/n/^C) >> warning: pharo-vm/PharoV30.sources is probably truncated >> Build step 'Execute shell' marked build as failure >> Archiving artifacts >> Recording test results > >

Feb. 23, 2015

[pharo-project/pharo-core] 7e744b: 40499

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7e744bae139486c46829ba22e8f7fe2d9573dc43 https://github.com/pharo-project/pharo-core/commit/7e744bae139486c46829ba22… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-23 (Mon, 23 Feb 2015) Changed paths: A FileSystem-Core.package/AbstractFileReference.class/instance/enumerating/allChildrenMatching_.st A FileSystem-Core.package/AbstractFileReference.class/instance/enumerating/allDirectoriesMatching_.st M FileSystem-Core.package/AbstractFileReference.class/instance/private/childGeneratorBlock_matching_.st M Graphics-Transformations.package/MorphicTransform.class/class/instance creation/offset_angle_scale_.st M Graphics-Transformations.package/MorphicTransform.class/instance/accessing/withAngle_.st M Graphics-Transformations.package/MorphicTransform.class/instance/accessing/withOffset_.st M Graphics-Transformations.package/MorphicTransform.class/instance/accessing/withScale_.st M Graphics-Transformations.package/MorphicTransform.class/instance/private/setAngle_.st M Graphics-Transformations.package/MorphicTransform.class/instance/private/setOffset_angle_scale_.st M Graphics-Transformations.package/MorphicTransform.class/instance/private/setScale_.st M ProfStef-Core.package/PharoSyntaxTutorial.class/instance/interactive/divideTwoByZero.st R ProfStef-Core.package/PharoSyntaxTutorial.class/instance/lessons/instanciation.st A ProfStef-Core.package/PharoSyntaxTutorial.class/instance/lessons/instantiation.st M ProfStef-Core.package/PharoSyntaxTutorial.class/instance/tutorial/tutorial.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script499.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40499.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40499 14971 MorphicTransform: Better Argument Names https://pharo.fogbugz.com/f/cases/14971 14961 instantiation is misspelled in PharoSyntaxTutorial https://pharo.fogbugz.com/f/cases/14961 14947 Missing allChildrenMatching: https://pharo.fogbugz.com/f/cases/14947 http://files.pharo.org/image/40/40499.zip

Feb. 23, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40499 Home: https://github.com/pharo-project/pharo-core

Feb. 23, 2015

Re: [Pharo-dev] Determine if a method is Jitted or not

by Thierry Goubier

2015-02-23 16:36 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Thierry, > > there's an unadvertised primitive called Context>>#xRay (or > ContextPart>>#xRay) that answers these questions for tests. I'm away from > the system right now but I'll get you the source soon. Also, the limit on > jutting methods, 60 literals, is a default. There's a command line option > -maxcoglits (IIRC) that you can change. > Thanks Eliot! It's helping a lot to guide me, even if I have to work at the ast level and, as a result, I estimate the number of literals in the bytecode by counting the number of literal nodes in the AST, with the approximation that ~100 literal nodes will make it under the limit. Making it under the limit shaves 30% of the execution time of a parse with SmaCC. And it avoids the too long methods as a side benefit. I would dream of having precise ways of estimating things like that on the AST. It's interesting to hit those "I'd like to be able to predict the performance of that piece of code" issues. Thierry > > Eliot (phone) > > On Feb 23, 2015, at 5:05 AM, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > Hi All, > > > > anybody knows how to check if a method is jitted or not? > > > > I remember (maybe wrongly) that the Jit in Cog has a configurable limit > on the number of bytecodes for a method to be jitted or not; I'm looking > into the performance of generated code where I can, more or less, control > the length of methods (SmaCC) and I'd like to find the optimum point. > > > > Thanks, > > > > Thierry > >

Feb. 23, 2015

Re: [Pharo-dev] Determine if a method is Jitted or not

by Eliot Miranda

Hi Thierry, there's an unadvertised primitive called Context>>#xRay (or ContextPart>>#xRay) that answers these questions for tests. I'm away from the system right now but I'll get you the source soon. Also, the limit on jutting methods, 60 literals, is a default. There's a command line option -maxcoglits (IIRC) that you can change. Eliot (phone) On Feb 23, 2015, at 5:05 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi All, > > anybody knows how to check if a method is jitted or not? > > I remember (maybe wrongly) that the Jit in Cog has a configurable limit on the number of bytecodes for a method to be jitted or not; I'm looking into the performance of generated code where I can, more or less, control the length of methods (SmaCC) and I'd like to find the optimum point. > > Thanks, > > Thierry

Feb. 23, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 6e105e: 40498

by Marcus Denker

> On 23 Feb 2015, at 16:20, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/4.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 6e105eaf2fe849f630afc1aae35355b855ad1399 > https://github.com/pharo-project/pharo-core/commit/6e105eaf2fe849f630afc1aa… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2015-02-23 (Mon, 23 Feb 2015) > > Changed paths: > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script498.st > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40498.st > M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > > Log Message: > ----------- > 40498 > 14961 instantiation is misspelled in PharoSyntaxTutorial > https://pharo.fogbugz.com/f/cases/14961 > > 14947 Missing allChildrenMatching: > https://pharo.fogbugz.com/f/cases/14947 > > 14971 MorphicTransform: Better Argument Names > https://pharo.fogbugz.com/f/cases/14971 No, this one is empty. Strange. I will do a manual update next. Marcus

Feb. 23, 2015

Fwd: Build failed in Jenkins: NeoCSV Â» 40,stable,vm #474

by Sven Van Caekenberghe

Disk full on the contribution CI ... > Begin forwarded message: > > Date: 23 Feb 2015 16:26:46 CET > From: ci-pharo-contribution(a)inria.fr > To: sven(a)stfx.eu > Subject: Build failed in Jenkins: NeoCSV Â» 40,stable,vm #474 > > See <https://ci.inria.fr/pharo-contribution/job/NeoCSV/PHARO=40,VERSION=stable,V…> > > ------------------------------------------ > Started by upstream project "NeoCSV" build number 475 > originally caused by: > Started by timer > Building remotely on pharo-contribution-linux64.ci.inria.fr (32 64 linux) in workspace <https://ci.inria.fr/pharo-contribution/job/NeoCSV/PHARO=40,VERSION=stable,V…> > > Deleting project workspace... [vm] $ /bin/sh -xe /tmp/hudson5392095292005988537.sh > + export JOB_NAME=NeoCSV > + bash > + wget --quiet -O - get.pharo.org/40+vm > Downloading the latest 40 Image: > http://files.pharo.org/image/40/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Downloading PharoV30.sources: > http://files.pharo.org/sources//PharoV30.sources.zip > pharo-vm/PharoV30.sources: write error (disk full?). Continue? (y/n/^C) > warning: pharo-vm/PharoV30.sources is probably truncated > Build step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results

Feb. 23, 2015