- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] potential to include cryptography in base image

by Peter UhnÃ¡k

> Alright, please let me know. If someone shows me how to get this into > configurations and the Catalog, we'll get it done. You just need to commit your configuration to MetaRepoForPharo50 (this should be public repo; if you can't commit ask on the mailing list and someone will add you). But before you do that, open Versionner (World > Tools > Versionner), right click your configuration and select "add catalog methods". This will add class-side methods to the Configuration class which you can modify to write things like description, website, tags, etc. You can also use the Veresionner to create your ConfigurationOf if you don't have one already, more info on Configurations can be found in DeepIntoPharo (Metacello chapter) https://ci.inria.fr/pharo-contribution/view/Books/job/DeepIntoPharo/lastSuc… or look through other configurations in the image or search through mailing list archives, there should be plenty of information. Peter

Dec. 15, 2015

Re: [Pharo-dev] potential to include cryptography in base image

by Robert Withers

On 12/15/2015 05:20 AM, Sven Van Caekenberghe wrote: > Robert, > > I think that the Pharo community, part of which is more business oriented, is absolutely interested in more and better Crypto code. In any case, I am. > > What we absolutely want, if it is not already the case (I did not check), is that the Crypto code can be loaded using 1 single action (through our validated Monticello configurations and Catalog mechanism) - I am sure you will find help to achieve and maintain (through a CI process) that goal. Alright, please let me know. If someone shows me how to get this into configurations and the Catalog, we'll get it done. robert > > Whether it should be a base part of the image is another question. Modularity is a huge goal for Pharo. This is a much harder discussion (as the same can be said of or asked for for many packages that are generally useful: XML, CSV, JSON, SQL, ...). In any the case, the first step is the one described in the previous paragraph. Then you need traction, usage, and maybe demand for full inclusion. > > Regards, > > Sven > >> On 15 Dec 2015, at 11:00, Robert Withers <robert.w.withers(a)gmail.com> wrote: >> >> It was suggested to me that I write to the list and raise the question about cryptography being included in the base image. Really I have 3 questions I would ask you all: >> >> â¢ is it desirable to include cryptography? >> â¢ is it feasible to include cryptography? >> â¢ what is the time frame for including cryptography? >> Given the thread on password hashing (and salting and so on), there are good, solid implementations in the cryptography package. Looking in the Cryptography repository, there is a Pharo 5.0 compatible Cryptography package. >> >> In light of another recent thread discussing random number generation, discussion about the best approach to random algorithms in cryptography ought be engaged. For instance, the SecureRandom algorithm evidently provides some level of guarantee. >> >> To underline the solidity I am attaching a profile of all 102 cryptography tests passing green. This profile demonstrates that there are no areas of particular inefficiency - nothing stands out to be improved - means that the entire library is maximally efficient. >> >> And so I please ask that we have these discussions, for there is a lot of value in this package for general and basic use. >> >> >> -- >> . .. ... ^,^ best, robert >> <Cryptography Spy Results.text.gz> -- . .. .. ^,^ best, robert

Dec. 15, 2015

Re: [Pharo-dev] AsmJit

by ClÃ©ment Bera

We're getting away from Jan initial question here ... I think the point here is that Cog has: - 2 stable back ends: ARMv5 and x86 - 2 backends stable in the simulator with production planned for ~ April: x64 and MIPS and Tim is willing to do the ARMv8 backend. All the 4, and soon 5, cog back ends are maintained: - x86 and x64 maintained by Eliot - MIPS maintained by Ryan - ARMv5 and soon ARMv8 maintained by Tim Each backend requires months of work. Do you want to maintain 10 backends instead of 5 ? Do want to spend time to implement 5 backends or 10 ? I don't. Only the x86 backend is duplicated right now in AsmJIT. So one idea is to reuse Cog's backends from the image instead of AsmJIT. To do so, we can use encodings available in the sista extended instruction set to tell Cog what machine code to generate. A project named uFFI aims, among other things, at doing this, by providing a unified interface between the Cog backends and AsmJIT. 2015-12-15 16:43 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Jan, > > > On Dec 15, 2015, at 3:06 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > > > > Hi guys, > > > > two queations: > > > > (i) Is AsmJit going to be developed any more or it's abandoned > > as well as native boost? > > AsmJIT is effectively being abandoned but NativeBoost is not. > > The key limitation of AsmJIT is that it was not designed to be cross > platform; it is effectively an x86 assembler. As such it's use gets in the > way of ARM and x86_64 (I am currently getting the C version of 64-bit Cog > Spur working on x86_64, given that it is working in the simulator). > > Another limitation is that it doesn't play that well with the VM's JIT. > Igor and I never managed to work on integrating it better. The VM's job is > managing code and Igor's approach was to hack; eliminating execution > protection in the entire heap, instead of extending the support that either > the Alien plugin's callback support or the JIT's executable method zone > provides. Making the entire heap executable is /not/ a sensible approach. > > But there is a better way! A key component of the Sista adaptive > optimizer/speculative inlined that ClÃ©ment is currently stabilizing (!!) is > a set of bytecodes that encode unsafe operations like at:put: without > bounds, type or store checks. For example, the normal at:put: is about a > hundred instructions, checks for smallinteger indices, differentiates > between byte, 32-but long and pointer objects and does a store check. But > one of the Sista codes for at:put: generates about two instructions, one to > adjust the index, the other to do the store. Distaste job is to analyze > code and inline methods using these unsafe bytecodes where they are proven > to be safe, hence increasing performance. > > Unlike AsmJIT, Sista's unsafe bytecodes are cross platform, and, being > executed by the VM, can work on an interpreter VM or be converted to > machine code by the JIT. > > So our plan is to extend these bytecodes with ones that support marshaling > arguments for NativeBoost calls. Ronie Salgado has already extended his > lowcode scheme to define these instructions and sometime soon (hopefully > 2016) we shall rewrite NativeBoost to target these bytecodes. > > HTH > > > (ii)Where can I find latest AsmJit? I'm properly confused: > > > > * Is is the one in latest Pharo 4.0 (5.0) image? > > * Is it the one here: http://smalltalkhub.com/#!/~Pharo/AsmJit ? > > (the one in the image seem to be based on completely disjunct > > set of .mcz than those in the repo above). > > > > Best, Jan > > _,,,^..^,,,_ (phone) >

Dec. 15, 2015

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: Unicode Support))

by Mark Bestley

On 15/12/2015 16:05, H. Hirzel wrote: > On 12/15/15, Ben Coman <btc(a)openinworld.com> wrote: >> On Thu, Dec 10, 2015 at 12:37 AM, Todd Blanchard <tblanchard(a)mac.com> >> wrote: >>> They are practically the same thing. >>> >>> ICU was developed by Taligent which was a joint venture between Apple and >>> IBM. Makes sense that NSString and ICU's UnicodeString are pretty close >>> in implementation. ICU was also ported to Java for Sun by IBM. The point >>> is - this is a very elaborate chunk of code with far reach. If ICU is >>> wrong on some point - it is universally wrong and thus likely to be taken >>> as "right" as it is at least consistent. I think re-implementing it is >>> folly TBH. Just use it. >> I suspect the history is wrong as NSString was first written at NeXT when they were not Apple and was not unicode aware at first, but the end result does seem to be NSString now uses ICU >> Apple seem to have moved on from NSString to support Unicode in a >> different way in Switft... > > Could you please give some more details? > > I have read > https://www.objc.io/issues/9-strings/unicode/#nsstring-and-unicode > so far. > > It says that an NSString object actually represents an array of > UTF-16-encoded code units. > > This in contrast to Squeak / Pharo where a String is an > ArrayedCollection of 21 bit Unicode code points (transparently > optimizing to a ByteArray if the string only contains values of the > first code page). > > The Swift code (well for the next version) is open source see https://github.com/apple/swift-corelibs-foundation for the Foundation lib which includes Strings. Foundation is being rewritten in Swift rather than Objective C so should be Swift->C but I wonder if it is really clean yet, i.e. do they need all the current code. A quick scan gives the low level as Stringing (same as current OSX_. The encodings and conversions seem to use ICU to do the work (which is UTF-16 based) Also in NSString.swift is the line public typealias unichar = UInt16 >>> >>>> On Dec 8, 2015, at 15:52, EuanM <euanmee(a)gmail.com> wrote: >>>> >>>> Equally old are the NextStep Object C functions which are now embodied >>>> within MacOS X. >>>> -- Mark

Dec. 15, 2015

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

by H. Hirzel

On 12/15/15, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Dec 10, 2015 at 12:37 AM, Todd Blanchard <tblanchard(a)mac.com> > wrote: >> They are practically the same thing. >> >> ICU was developed by Taligent which was a joint venture between Apple and >> IBM. Makes sense that NSString and ICU's UnicodeString are pretty close >> in implementation. ICU was also ported to Java for Sun by IBM. The point >> is - this is a very elaborate chunk of code with far reach. If ICU is >> wrong on some point - it is universally wrong and thus likely to be taken >> as "right" as it is at least consistent. I think re-implementing it is >> folly TBH. Just use it. > > Apple seem to have moved on from NSString to support Unicode in a > different way in Switft... Could you please give some more details? I have read https://www.objc.io/issues/9-strings/unicode/#nsstring-and-unicode so far. It says that an NSString object actually represents an array of UTF-16-encoded code units. This in contrast to Squeak / Pharo where a String is an ArrayedCollection of 21 bit Unicode code points (transparently optimizing to a ByteArray if the string only contains values of the first code page). >> >>> On Dec 8, 2015, at 15:52, EuanM <euanmee(a)gmail.com> wrote: >>> >>> Equally old are the NextStep Object C functions which are now embodied >>> within MacOS X. >>> >> >> > >

Dec. 15, 2015

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

by Todd Blanchard

I wouldn't say that necessarily. There's a whole lot of API that is dependent on objective c - I suspect they have a toll free bridging in there where swift/objective c strings share enough common protocol to be fully substitutable like with CFString. Anyhow swifts step away from smalltalk ideals and the added complexity of language bridging has me avoiding it. Sent from the road > On Dec 15, 2015, at 00:49, Ben Coman <btc(a)openinworld.com> wrote: > > Apple seem to have moved on from NSString to support Unicode in a > different way in Switft...

Dec. 15, 2015

Re: [Pharo-dev] AsmJit

by Eliot Miranda

Hi Jan, > On Dec 15, 2015, at 3:06 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > > Hi guys, > > two queations: > > (i) Is AsmJit going to be developed any more or it's abandoned > as well as native boost? AsmJIT is effectively being abandoned but NativeBoost is not. The key limitation of AsmJIT is that it was not designed to be cross platform; it is effectively an x86 assembler. As such it's use gets in the way of ARM and x86_64 (I am currently getting the C version of 64-bit Cog Spur working on x86_64, given that it is working in the simulator). Another limitation is that it doesn't play that well with the VM's JIT. Igor and I never managed to work on integrating it better. The VM's job is managing code and Igor's approach was to hack; eliminating execution protection in the entire heap, instead of extending the support that either the Alien plugin's callback support or the JIT's executable method zone provides. Making the entire heap executable is /not/ a sensible approach. But there is a better way! A key component of the Sista adaptive optimizer/speculative inlined that ClÃ©ment is currently stabilizing (!!) is a set of bytecodes that encode unsafe operations like at:put: without bounds, type or store checks. For example, the normal at:put: is about a hundred instructions, checks for smallinteger indices, differentiates between byte, 32-but long and pointer objects and does a store check. But one of the Sista codes for at:put: generates about two instructions, one to adjust the index, the other to do the store. Distaste job is to analyze code and inline methods using these unsafe bytecodes where they are proven to be safe, hence increasing performance. Unlike AsmJIT, Sista's unsafe bytecodes are cross platform, and, being executed by the VM, can work on an interpreter VM or be converted to machine code by the JIT. So our plan is to extend these bytecodes with ones that support marshaling arguments for NativeBoost calls. Ronie Salgado has already extended his lowcode scheme to define these instructions and sometime soon (hopefully 2016) we shall rewrite NativeBoost to target these bytecodes. HTH > (ii)Where can I find latest AsmJit? I'm properly confused: > > * Is is the one in latest Pharo 4.0 (5.0) image? > * Is it the one here: http://smalltalkhub.com/#!/~Pharo/AsmJit ? > (the one in the image seem to be based on completely disjunct > set of .mcz than those in the repo above). > > Best, Jan _,,,^..^,,,_ (phone)

Dec. 15, 2015

Re: [Pharo-dev] [Pharo-users] [IMPORTANT] Starting migration to Spur VM

by Johan Fabry

Sorry for the stupid question, but how should I adapt my CI job? I saw that the last build failed with no tests being run, so I guess this was due to the VM being changed. > On Dec 14, 2015, at 07:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Dec. 15, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 6a48f4: 50499

by Esteban Lorenzano

partially workedâ¦ but I will need a new one :( Esteban > On 15 Dec 2015, at 16:03, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 6a48f484555b8ff8ae9faa567347dc8615bebbf2 > https://github.com/pharo-project/pharo-core/commit/6a48f484555b8ff8ae9faa56… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2015-12-15 (Tue, 15 Dec 2015) > > Changed paths: > M FFI-NB.package/FFIMethodRegistry.class/class/class initialization/initialize.st > A FFI-NB.package/FFIMethodRegistry.class/class/class initialization/initializeStartUpList.st > M FFI-NB.package/FFIMethodRegistry.class/instance/accessing/checkPlatform.st > A FFI-NB.package/FFIMethodRegistry.class/instance/accessing/reset.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50498.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50499.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50498.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50499.st > > Log Message: > ----------- > 50499 > 17241 ffi-nb is not cleaning compiled methods. then they fail when platform changes > https://pharo.fogbugz.com/f/cases/17241 > > http://files.pharo.org/image/50/50499.zip > >

Dec. 15, 2015

[pharo-project/pharo-core]

by GitHub

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

Dec. 15, 2015