- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Nov. 19, 2014

Nov. 19, 2014

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

1 0

Can we make this fast ?
by phil＠highoctane.be Nov. 19, 2014

Nov. 19, 2014

See https://news.ycombinator.com/item?id=8625280 [ (1 to: 100000000) sum ] timeToRun Here we get out of the SmallInteger range... Apart FFI'ing the thing, do we have other options? Phil

5 7

Pharo contributions server gone
by Torsten Bergmann Nov. 19, 2014

Nov. 19, 2014

https://ci.inria.fr/pharo-contribution Restart?

2 1

Emergency tool instead of the debugger starting (caused by issue #14469 in update #40373)
by Torsten Bergmann Nov. 19, 2014

Nov. 19, 2014

The expression 1 halt or any other part that has to be debugged gives the emergency tool instead of the debugger. Pharo 4.0 #40372 image is working (gives the usual debugger) Pharo 4.0 #40373 image not working (emergency evaluator) The problem seems to be related to the fix/slice "SLICE-Issue-14469-Merge-back-OrderPreservingDictionary-improvements-MarcusDenker.1" for issue 14469. When one manually merges the slice from issue #14469 into Pharo 4.0 #40372 one can reproduce this problem. https://pharo.fogbugz.com/f/cases/14496

2 1

Re: [Pharo-dev] [Vm-dev] Re: Spur 64-bits. Ugh, this could be a slog...
by David T. Lewis Nov. 19, 2014

Nov. 19, 2014

On Tue, Nov 18, 2014 at 07:59:30PM -0800, Ryan Macnak wrote: > > What about bytecode pc's? These are indexed based on the physical size of > the literals. I don't like the idea of debugging pc -> source mappings, pc > coverage data, etc needing invalidation after starting an image on a > platform with a different word size. I may be misunderstanding your question, but I do not think that this will be an issue. All byte addressible objects need to work properly in any image, including 32 and 64 bit images. If that part does not work, then the image will not run, so no problem ;-) With respect to platform word size (e.g. 64 bit OS versus 32 bit OS), the images should all run bit-identically regardless of platform word size. A 64-bit image can (and does) run on a 32-bit host platform, given a suitably compiled VM. And a 32-bit image will run on a 64-bit host platform, given a suitably compiled VM (or more commonly, a 32-bit VM with 32-bit compatibility libraries installed on the platform). Dave > > On Tue, Nov 18, 2014 at 7:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > Hi All, > > > > I'm making good progress on 64-bit Spur in the Stack VM simulator. > > But I've just noticed an image-level issue which could be indicative of > > lots of 32-bit assumptions baked into the Squeal/Pharo/Newspeak systems. > > > > SmallInteger>>digitAt: n > > "Answer the value of an indexable field in the receiver. > > LargePositiveInteger uses bytes of base two number, and each is a 'digit' > > base 256. Fail if the argument (the index) is not an Integer or is out of > > bounds." > > n>4 ifTrue: [^ 0]. > > self < 0 > > ifTrue: > > [self = SmallInteger minVal ifTrue: > > ["Can't negate minVal -- treat specially" > > ^ #(0 0 0 64) at: n]. > > ^ ((0-self) bitShift: (1-n)*8) bitAnd: 16rFF] > > ifFalse: [^ (self bitShift: (1-n)*8) bitAnd: 16rFF] > > > > This assumes that SmallInteger is only ever 4 bytes, which is unacceptably > > wasteful for my approach to 64-bits. In 64-bit Spur, SmallIntegers are > > 61-bit 2's complement. > > > > I'm raising this example at this point to see if the community might find > > similar issues and bring them to my attention. > > -- > > best, > > Eliot > >

1 0

Merge conflict for "META Case: restructure Tests and test packages"
by Nicolai Hess Nov. 18, 2014

Nov. 18, 2014

for example : https://pharo.fogbugz.com/default.asp?14433 I don't why there is a merge conflict, maybe it is how the slice is created. I think the restructuring (moving all classes from XXXTest to XXX-Tests) would work if we delete the empty XXXTests package before creating the slice. nicolai

2 2

Pharo contribution Jenkins offline
by Yuriy Tymchuk Nov. 18, 2014

Nov. 18, 2014

Can someone (re)boot it? Thanks Uko

1 0

GLViewportMorph>>#layoutInBounds:
by Yuriy Tymchuk Nov. 18, 2014

Nov. 18, 2014

Hi, can someone advise me how to deal with one issue. I put Roassal3D morph is a spec composite model, and when I open the window I get 'Frame buffer is incomplete: GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENTâ error because GLViewportMorph>>#layoutInBounds: bounds attribute has a zero coordinate. Should there be a guard in the method of GLViewportMorph, or I should do something in Spec? Uko

3 7

[pharo-project/pharo-core]
by GitHub Nov. 18, 2014

Nov. 18, 2014

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

1 0

[pharo-project/pharo-core] bbcff2: 40374
by GitHub Nov. 18, 2014

Nov. 18, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bbcff2e688d4845d9f9e18b2b6630358f8c6b410 https://github.com/pharo-project/pharo-core/commit/bbcff2e688d4845d9f9e18b2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-18 (Tue, 18 Nov 2014) Changed paths: A Growl.package/GrowlMorph.class/class/settings/growlPositionChoices.st A Growl.package/GrowlMorph.class/class/settings/growlSettingsOn_.st R Kernel.package/Integer.class/class/prime numbers/verbosePrimesUpTo_.st R Kernel.package/Integer.class/class/prime numbers/verbosePrimesUpTo_do_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script374.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40374.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Settings-Polymorph.package/PolymorphSystemSettings.class/class/growl/growlPosition.st R Settings-Polymorph.package/PolymorphSystemSettings.class/class/growl/growlPositionChoices.st R Settings-Polymorph.package/PolymorphSystemSettings.class/class/growl/growlPosition_.st R Settings-Polymorph.package/PolymorphSystemSettings.class/class/growl/growlSettingsOn_.st M Settings-Polymorph.package/PolymorphSystemSettings.class/class/settings/appearanceSettingsOn_.st M System-Support.package/SystemNavigation.class/instance/query/methodsWithUnboundGlobals.st Log Message: ----------- 40374 14385 move growl settings to Growl class https://pharo.fogbugz.com/f/cases/14385 14484 Remove debugging methods from Integer https://pharo.fogbugz.com/f/cases/14484 13982 Failing test: ReleaseTest>>testMethodsWithUnboundGlobals https://pharo.fogbugz.com/f/cases/13982 http://files.pharo.org/image/40/40374.zip

1 0