Object Spaces with dedicated GC and possibly dedicated cpu looks like a better idea than a flat 64bit VM and OE to me. Le 27 juin 2013 21:43, "Clément Bera" <[email protected]> a écrit :
> 2013/6/27 kilon <[email protected]> > >> Just for the notice, because I stirred up the whole discussion about 64 >> bit >> pharo. >> >> To my knowledge the whole point of having a 64 bit app is that so that app >> can access more than 4 GBs of Ram. Is that the case or I have no clue >> what I >> am talking about ? >> > > Yeah actually the goal is to allow the user to work on Pharo without > installing 32bits lib and to be able to call 64 bits external libraries > instead of 32 bits ones. > > >> >> I have read that already Pharo VM has some restrictions on how much ram an >> image can use. Obviously even for todays standard 4GBs for a single app >> is a >> bit excessive but if pharo apps continue to grow in complexity and we >> start >> to venture in areas of demanding ram needs , then it wont be hard to brake >> that 4GB barrier. >> > > You are right, we don't care about the RAM size, even language as Java > does not have a VM with a GC supporting more that much of RAM. > > >> >> In any case maybe before you invest so much effort you must clear up what >> the real benefits would be for us the users of pharo if pharo goes 64 bit. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Pharo-dev-How-do-can-we-set-up-a-crowdsourcing-for-pharo-tp4695637p4695793.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > -- > Clément Béra > Mate Virtual Machine Engineer > Bâtiment B 40, avenue Halley 59650 *Villeneuve d'Ascq* >
