And in Windows land, "long" is 32 bits even for 64 bit apps...
Even after you're done with the VM part, someone will have to go audit all the external interfaces and make sure they really follow the manual.
On 4/1/14 21:24 , p...@highoctane.be wrote:
How would that work? Would this be a 32 bit Object memory and engine compiled in 64bit mode? How is the code amended to make that possible? Is there a source tree somewhere? There are "int"s all over the place, so, how do we handle this? For the Slang part it appears doable. For the support code, especially Windows, it looks harder. TIA Phil Le 2 avr. 2014 01:07, "Clément Bera" <bera.clem...@gmail.com <mailto:bera.clem...@gmail.com>> a écrit : Hey, For 64 bits Spur is a big step forward. For Christmas you should have at least the stack VM in 64bits. The JIT may take a bit longer to port. Esteban and Eliot will work on that starting from May. There's also the solution to compile the VM in 64bits with a 32bits runtime (I think FFI does not work, but the VM works in 64bits environment, as gettimothy posted on vm-dev). 2014-03-29 13:18 GMT-07:00 Pharo4Stef <pharo4s...@free.fr <mailto:pharo4s...@free.fr>>: On 29 Mar 2014, at 21:16, Roelof Wobben <r.wob...@home.nl <mailto:r.wob...@home.nl>> wrote: > Pharo4Stef schreef op 29-3-2014 21:07: >> >> >>> Pity. >> >> You know there is no magic powder. We are already really grateful that eliot is pushing the vm work. >> Esteban will help on the 64 bits and clement probably too or spur and new bytecodes plus language side optimisations. If we could pay 3 full time engineers in the future… but this is not the case. >> > > I know that and it's not that i think the developer do a bad job. > It's more a expresiion of my feeling. Ok then I share the same feeling :) > > Roelof >
