Test cases status - Windows

[greenozon]

after successfully bulding the full package (including llvm) I did run some subset under windows
the quesitons are

1. why do we have different results when running with default options and using sequential run (-m flag)
2. here is the failed TC when running with -m

c:\Dev\re\miasm\test>python test_all.py -o python -m
 TEST\ARCH x86/sem.py python
DONE x86/sem.py python 0s
 TEST\ARCH x86/unit/mn_stack.py python
DONE x86/unit/mn_stack.py python 1s
 TEST\ARCH x86/unit/mn_das.py python
DONE x86/unit/mn_das.py python 3s
 TEST\ARCH x86/unit/mn_pshufb.py python
DONE x86/unit/mn_pshufb.py python 0s

....

Result: 136/137 pass
ERROR jitcore.py python
b'Traceback (most recent call last):\r\n  File "c:\\Dev\\re\\miasm\\test\\jitter\\jitcore.py", line 12, in <module>\r\n    jitter.cpu.RAX = -1\r\n    ^^^^^^^^^^^^^^\r\nTypeError: Arg too big for uint64_t\r\n'

I'm curious how come that this speicific TC fails... is -1 value bigger then uint64_t type?

[greenozon]

After reading some materials come to conclusion that due to differences in OS and compilers, there is differnet behaviour of handing uint64_t values
Under Windows python does not allow to set negative values into unsigned type (uint64_t)
so here is a PR to address this corner case: #1501