Hi Clement,
it's been a while since I last tested, but in a few words:
- win64 use it's own ABI
- we have to assign the registers differently than sysV
- the experiments I did resulted in VM crashing early (before opening window)

Nicolas

2017-03-19 20:29 GMT+01:00 Clément Bera <bera.clement@gmail.com>:
 
Thank you very much for doing Nicolas. It is very important for many Pharo users to use Pharo 64 bits on Windows.

What are the problems you have when trying to build the VM with the JIT that you don't have when building the stack VM ? Is it about API to make the memory executable, is it about calling conventions ?

On Sun, Mar 19, 2017 at 12:14 PM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
 

2017-03-19 17:31 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:
Hi,
I've built a 64bits pharo.stack.spur VM for windows on my machine,
and I'm uploading the changes to opensmalltalk-vm in branch
build_pharo_win32_with_cygwin

If the appveyor job correctly succeed, I will emit a pull request.

The VM does not have the SqueakSSL plugin yet.

The 64bits squeak/pharo.cog.spur JIT for windows is still to come,
but I did not work on it for a few months...
One thing at a time.

Let's cross finger

Nicolas