- Pharo-dev - lists.pharo.org

for opal compiler developer: issue on calculating the frameSize
by Nicolai Hess Dec. 3, 2014

Dec. 3, 2014

I uploaded a cs fix_closure_stack_frame_size_computation for this issue 13854 <https://pharo.fogbugz.com/default.asp?13854> frameSize calculated wrongly for #lineSegmentsDo: ! It is not meant as a fix but to show and make it easier to understand where the bug is. I don't like this fix because it looks like "fixing the right bug at the wrong place" About the issue: It is all about calculating the correct stack frame size for a compiled method (compiledmethod>>#header) With opal, the result is sometimes larger than it is needed or to small (strangly enough, although we have *some* methods with a too small stack frame, a vm crash only happens for me if I am stepping through the method with the debugger). The needed stack frame size is calculated from the numTemps (arguments + number of temporaries) + the max stack depth *and* if the method defines any blocks the methods stack frame size is the maximum of - its own needed stack frame size - all of its blocks needed stack frame sizes. (And what makes this calculation a little bit tricky, the methods arguments and tempvars, although it looks like that, don't influence the stack frame size for the blocks. Every block context starts with its own stack) nicolai

3 2

[pharo-project/pharo-core] 4035b4: 40397
by GitHub Dec. 3, 2014

Dec. 3, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4035b411d8b30af9d9482d9ccad7532a91afd714 https://github.com/pharo-project/pharo-core/commit/4035b411d8b30af9d9482d9c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-03 (Wed, 03 Dec 2014) Changed paths: M AsmJit-x86.package/AJx86InstructionDescription.class/instance/emitting/emitsmnemonic_operand1_operand2_operand3_.st A OpalTools.package/extension/LiteralVariable/instance/gtInspectorUsersIn_.st A OpalTools.package/extension/Slot/instance/gtInspectorUsersIn_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script397.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40397.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Slot.package/GlobalVariable.class/instance/as yet unclassified/definingClass.st A Slot.package/GlobalVariable.class/instance/queries/definingClass.st Log Message: ----------- 40397 14033 Failing test: AJx64AssemblerTests>#testStringOps64Mnemonics https://pharo.fogbugz.com/f/cases/14033 14562 add a Users tab to GTInspector for Slots and LiteralVariables https://pharo.fogbugz.com/f/cases/14562 http://files.pharo.org/image/40/40397.zip

1 0

[pharo-project/pharo-core]
by GitHub Dec. 3, 2014

Dec. 3, 2014

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

1 0

Re: [Pharo-dev] Athens Repository (NativeBoost)
by Nicolai Hess Dec. 3, 2014

Dec. 3, 2014

2014-11-24 23:34 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > both are integrated into the image. > while NB has been maintained directly, athens should still be loadable (if > not the caseâ¦ we have a problem for the future :P). > what does that mean for athens, yes unload and loadable from the image or loadable from the sthub repository? > > yes, we are slowly moving in the opposite direction of âall maintained in > the imageâ, and eventually we plan/dream to have a small kernel and a bunch > of configurations to produce Pharo. > > now, about NB, we do not have special plans. > it is in the image and it will be maintained as part of Pharo. > > now, since the most common use of NB is for FFI, and NB is not present in > all platforms, we are working (Ronie, in this case) in a âunified FFIâ, > which will provide a common abstraction layer for several FFI frameworks > (NB, OldFFI, Alienâ¦). With that, we can choose which one of the frameworks > we use depending on the situation (but ideally, we will maintain just one, > the one that fits better in Pharo). > Againâ¦ this are just ideas for the future :) > > Esteban > > > > On 24 Nov 2014, at 23:23, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2014-11-24 20:41 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > >> Hi, >> >> were is NB currently maintained? Only within the image as it is integrated >> or still with an external config and on STHub? >> >> The reason why I ask: when I load the latest NB-Core package >> from STHub it looks like this one is outdated and back from Pharo3 day >> (trying to load it gives problems from changes in Pharo 4). >> >> So it looks like NB was originally developed external using STHub, then >> integrated >> into standard image and now it is only internally in-image managed. OK. >> >> But the future goal is as far as I understood to manage more and >> more packages using external configs again. >> >> What is the status and future plan for NB? Will the repo get >> synchronized? Or will it stay internal only? >> >> Thx >> T. >> >> > I was about to ask the same question for Athens, the packages in pharo4 > and sthub diverge. > I can merge the sthub and pharo4 version for Athens (and mabe NB), I just > don't know what > is the plan for the feauture, manage packages for Athens and NB in the > image or on sthub. > > >

5 10

[pharo-project/pharo-core]
by GitHub Dec. 3, 2014

Dec. 3, 2014

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

1 0

[pharo-project/pharo-core] bc3f9f: 40396
by GitHub Dec. 3, 2014

Dec. 3, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bc3f9f3572b81f74918cf66da2981dc2ed9e2a26 https://github.com/pharo-project/pharo-core/commit/bc3f9f3572b81f74918cf66d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-03 (Wed, 03 Dec 2014) Changed paths: A AST-Interpreter-Test.package/InterpreterTest.class/class/testing/isAbstract.st A KernelTests.package/BooleanTest.class/instance/tests instance creation/testNew.st R KernelTests.package/BooleanTest.class/instance/tests/testBooleanNew.st R KernelTests.package/BooleanTest.class/instance/tests/testNew.st A KernelTests.package/FalseTest.class/instance/tests controlling/testAnd.st A KernelTests.package/FalseTest.class/instance/tests controlling/testIfFalse.st A KernelTests.package/FalseTest.class/instance/tests controlling/testIfFalseIfTrue.st A KernelTests.package/FalseTest.class/instance/tests controlling/testIfTrue.st A KernelTests.package/FalseTest.class/instance/tests controlling/testIfTrueIfFalse.st A KernelTests.package/FalseTest.class/instance/tests controlling/testOr.st A KernelTests.package/FalseTest.class/instance/tests converting/testAsBit.st A KernelTests.package/FalseTest.class/instance/tests instance creation/testNew.st A KernelTests.package/FalseTest.class/instance/tests logical operations/testAND.st A KernelTests.package/FalseTest.class/instance/tests logical operations/testNot.st A KernelTests.package/FalseTest.class/instance/tests logical operations/testOR.st A KernelTests.package/FalseTest.class/instance/tests logical operations/testXor.st A KernelTests.package/FalseTest.class/instance/tests printing/testPrintOn.st R KernelTests.package/FalseTest.class/instance/tests/testAND.st R KernelTests.package/FalseTest.class/instance/tests/testAnd.st R KernelTests.package/FalseTest.class/instance/tests/testAsBit.st R KernelTests.package/FalseTest.class/instance/tests/testIfFalse.st R KernelTests.package/FalseTest.class/instance/tests/testIfFalseIfTrue.st R KernelTests.package/FalseTest.class/instance/tests/testIfTrue.st R KernelTests.package/FalseTest.class/instance/tests/testIfTrueIfFalse.st R KernelTests.package/FalseTest.class/instance/tests/testNew.st R KernelTests.package/FalseTest.class/instance/tests/testNot.st R KernelTests.package/FalseTest.class/instance/tests/testOR.st R KernelTests.package/FalseTest.class/instance/tests/testOr.st R KernelTests.package/FalseTest.class/instance/tests/testPrintOn.st R KernelTests.package/FalseTest.class/instance/tests/testXor.st R KernelTests.package/TrueTest.class/instance/testing/testAND.st R KernelTests.package/TrueTest.class/instance/testing/testAsBit.st R KernelTests.package/TrueTest.class/instance/testing/testNew.st R KernelTests.package/TrueTest.class/instance/testing/testNot.st R KernelTests.package/TrueTest.class/instance/testing/testPrintOn.st R KernelTests.package/TrueTest.class/instance/testing/testXor.st A KernelTests.package/TrueTest.class/instance/tests controlling/testAnd.st A KernelTests.package/TrueTest.class/instance/tests controlling/testIfFalse.st A KernelTests.package/TrueTest.class/instance/tests controlling/testIfFalseIfTrue.st A KernelTests.package/TrueTest.class/instance/tests controlling/testIfTrue.st A KernelTests.package/TrueTest.class/instance/tests controlling/testIfTrueIfFalse.st A KernelTests.package/TrueTest.class/instance/tests controlling/testOr.st A KernelTests.package/TrueTest.class/instance/tests converting/testAsBit.st A KernelTests.package/TrueTest.class/instance/tests instance creation/testNew.st A KernelTests.package/TrueTest.class/instance/tests logical operations/testAND.st A KernelTests.package/TrueTest.class/instance/tests logical operations/testNot.st A KernelTests.package/TrueTest.class/instance/tests logical operations/testOR.st A KernelTests.package/TrueTest.class/instance/tests logical operations/testXor.st A KernelTests.package/TrueTest.class/instance/tests printing/testPrintOn.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageIcon_.st A MonticelloGUI.package/extension/ThemeIcons/instance/newerPackagesAvailableIcon.st A MonticelloGUI.package/extension/ThemeIcons/instance/newerPackagesAvailableIconContents.st A NautilusRefactoring.package/extension/TClassDescription/instance/renameMethodAllItem_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script396.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40396.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Traits.package/TClassDescription.class/instance/as yet unclassified/renameMethodAllItem_.st Log Message: ----------- 40396 12810 Examine TrueTest and FalseTest for the possibility of a common superclass https://pharo.fogbugz.com/f/cases/12810 14558 Monticello icon tools should indicate newer available package versions https://pharo.fogbugz.com/f/cases/14558 14557 Failign test: #testUnCategorizedMethods https://pharo.fogbugz.com/f/cases/14557 14560 InterpreterTest isAbstract should return true as it is abstract (without tests) https://pharo.fogbugz.com/f/cases/14560 http://files.pharo.org/image/40/40396.zip

1 0

removing the last class extension of a class does not reclassify the class in nautilus
by stepharo Dec. 3, 2014

Dec. 3, 2014

Hi guys While refactoring critics and RB I got the following glitch. When I remove the class extension made by critics on RBRule, the RBRules were not systematically updated in the list of extension of the critics browser. It would be good to investigate this and https://pharo.fogbugz.com/default.asp?14561 BTW we should continue to simplify nautilus. :) Stef

1 0

Re: [Pharo-dev] contributing to Pharo testing effort
by sheridan＠sheridan-mahoney.com Dec. 3, 2014

Dec. 3, 2014

Hi Hilaire, I've been looking at this class (MultiByteFileStream) and I think I might have something to contribute. Cheers, Sheridan ------------------------------ Message: 8 Date: Mon, 24 Nov 2014 11:22:15 +0100 From: Hilaire <hilaire(a)drgeo.eu> To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] contributing to Pharo testing effort Message-ID: <m4v0sn$87d$1(a)ger.gmane.org> Content-Type: text/plain; charset=windows-1252 Hi Sheridan, The MultiByteFileStream is broken when dealing with non-ascii character (see my recent post "Something strange with fileOut) and there are only 3 tests for this class. Test stressing this class will be pretty useful to properly refactor it without breaking other parts. Hilaire Le 23/11/2014 19:45, sheridan(a)sheridan-mahoney.com a ?crit : >> Hi there, I am interested in helping out with writing tests in Pharo, >> and was wondering where would be a good place to start. I am familiar >> with Smalltalk from working at GemStone Systems in their QA department >> some years ago, but am somewhat new to Pharo. Any advice would be very >> appreciated. Best regards, Sheridan Mahoney > > -- > Dr. Geo - http://drgeo.eu [1] > iStoa - http://istoa.drgeo.eu [2] > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Pharo-dev mailing list > Pharo-dev(a)lists.pharo.org > http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org [3] > > ------------------------------ > > End of Pharo-dev Digest, Vol 19, Issue 148 > ****************************************** Links: ------ [1] http://drgeo.eu [2] http://istoa.drgeo.eu [3] http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org

1 0

Monticello repository-browser not emphasizing packages with newer versions.
by Ben Coman Dec. 2, 2014

Dec. 2, 2014

Hi Torsten, I really like the icons you added to Monticello https://pharo.fogbugz.com/default.asp?14451 however one thing I notice that seems lacking is indication of which packages have newer versions available. When clicking on a package on the left, on the right versions that are newer are shown in bold. It used to be that the corresponding packages on the left would also be bold, but now it does not. Do you have any ideas on how we can get bolded packages back in the left pane? cheers -ben

2 1

Re: [Pharo-dev] Pharo-dev Digest, Vol 19, Issue 151
by sheridan＠sheridan-mahoney.com Dec. 2, 2014

Dec. 2, 2014

To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] contributing to Pharo testing effort Message-ID: <547332E2.4080107(a)openInWorld.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed sheridan(a)sheridan-mahoney.com wrote: >> Hi there, I am interested in helping out with writing tests in Pharo, >> and was wondering where would be a good place to start. I am familiar >> with Smalltalk from working at GemStone Systems in their QA department >> some years ago, but am somewhat new to Pharo. Any advice would be very >> appreciated. Best regards, Sheridan Mahoney > > I can't direct you to a particular area, but (not that I've used it) > maybe you can try out Hapao to see if it helps you pick where the gaps > are. > > http://www.pharocasts.com/2011/04/test-coverage-with-hapao.html [1] > > http://hapao.dcc.uchile.cl/ [2] > > http://objectprofile.com/Hapao.html [3] > > cheers -ben > > P.S. I wonder if it would be practical to generate some Hapao reports > on > each Pharo build as a CI job - to be available as a ready reference for > such questions? > > *************************** Links: ------ [1] http://www.pharocasts.com/2011/04/test-coverage-with-hapao.html [2] http://hapao.dcc.uchile.cl/ [3] http://objectprofile.com/Hapao.html Hi Ben, Thanks for the pointers. I'll take a look at Hapeo as you suggest. It seems like a great idea to get an overall sense of what's going on where before I start. Cheers, Sheri

1 0