March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3875 in pharo: Merge minor NumberParser refactorings from Squeak

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3875 by stephane...(a)gmail.com: Merge minor NumberParser refactorings from Squeak http://code.google.com/p/pharo/issues/detail?id=3875 in 13111

March 25, 2011

Re: [Pharo-project] Issue 3876 in pharo: SqNumberParserTest>>testFloatGradualUnderflow has an odd condition

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 3876 by stephane...(a)gmail.com: SqNumberParserTest>>testFloatGradualUnderflow has an odd condition http://code.google.com/p/pharo/issues/detail?id=3876 in 13111

March 25, 2011

Re: [Pharo-project] Issue 3880 in pharo: Balloon Tests not categorized/commented in 1.3

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3880 by stephane...(a)gmail.com: Balloon Tests not categorized/commented in 1.3 http://code.google.com/p/pharo/issues/detail?id=3880 in 13111

March 25, 2011

Re: [Pharo-project] Issue 3876 in pharo: SqNumberParserTest>>testFloatGradualUnderflow has an odd condition

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #4 on issue 3876 by stephane...(a)gmail.com: SqNumberParserTest>>testFloatGradualUnderflow has an odd condition http://code.google.com/p/pharo/issues/detail?id=3876 (No comment was entered for this change.)

March 25, 2011

[Pharo-project] [update 1.3] #13110

by StÃ©phane Ducasse

13110 ----- - Issue 3881: Problem with Inst var refs.... Thanks Benjamin van Ryseghem. - Issue 3879: Wipe out positional arguments cruft from compiler. Thanks Igor Stasenko. - Issue 3859: Pluggin control. Thanks Igor Stasenko. - Issue 3715: Workspace shouting after switching between shout/unshout. Thanks Benjamin van Ryseghem. - Cleaning MCPackageManager. - Fixing some as yet unclassified categories. Stef and igor happy integrating and chatting about life :)

March 25, 2011

Re: [Pharo-project] Issue 3861 in pharo: Image freeze when changing system time

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3861 by stephane...(a)gmail.com: Image freeze when changing system time http://code.google.com/p/pharo/issues/detail?id=3861 (No comment was entered for this change.)

March 25, 2011

Re: [Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Comment #9 on issue 3715 by stephane...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 Benjamin you should talk with igor about using class new.

March 25, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Camillo Bruni

On 2011-03-25, at 18:12, Marcus Denker wrote: > > On Mar 25, 2011, at 5:51 PM, Marcus Denker wrote: > >> >> On Mar 25, 2011, at 5:46 PM, Camillo Bruni wrote: >>>> >>> >>> Arguing with absolute values is a bit dangerous: >>> >>> But it makes >>> 13ms / 17ms * 100% = 76% => 25% speed improvement! in COG >>> 50ms / 60ms * 100% = 83% => 17% faster > > So for Cog, you get this counter-intuitive result is because Cog > executes the overhead loop faster in combination with not jitting > what you wanted to test. I didn't run the benchmarks, I just listed the results mariano provided. Just to show that they do not provide a valid argument for removal of the method. So we have a nice Benchmarking framework on sqeaksource which we should use instead of relying on some pseudo valid results. I do not have to time right now to do so... but I expect the overhead to be neglectable in COG, since it should be fairly easy to JIT this in... > As the doit is *not* Jited, it executes as fast as in the intepreter case. > You see a higher percentage just because the base overhead loop > is executed faster and the thing you test gets a larger share of the > runtime. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 25, 2011

Re: [Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 3715 by stephane...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 in 13110

March 25, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Marcus Denker

On Mar 25, 2011, at 5:51 PM, Marcus Denker wrote: > > On Mar 25, 2011, at 5:46 PM, Camillo Bruni wrote: >>> >> >> Arguing with absolute values is a bit dangerous: >> >> But it makes >> 13ms / 17ms * 100% = 76% => 25% speed improvement! in COG >> 50ms / 60ms * 100% = 83% => 17% faster So for Cog, you get this counter-intuitive result is because Cog executes the overhead loop faster in combination with not jitting what you wanted to test. As the doit is *not* Jited, it executes as fast as in the intepreter case. You see a higher percentage just because the base overhead loop is executed faster and the thing you test gets a larger share of the runtime. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 25, 2011