Then, these two C types have corresponding RPython types: ``rffi.LONG``
and ``lltype.Signed`` respectively. The first should really correspond
-to the C ``long``. Add tests that check that integers cast
ed to one
+to the C ``long``. Add tests that check that integers cast to one
type or the other really have 32 and 64 bits respectively, on Win64.
Once these basic tests work, you need to review ``rpython/rlib/`` for
ages of ``rffi.LONG`` versus ``lltype.Signed``. The goal would be to
+uses of ``rffi.LONG`` versus ``lltype.Signed``. The goal would be to
fix some more ``LONG-versus-Signed`` issues, by fixing the tests --- as
always run on top of CPython64/64. Note that there was some early work
done in ``rpython/rlib/rarithmetic`` with the goal of running all the
with a minimal set of modules, starting with ``--no-allworkingmodules``;
you need to use CPython64/64 to run this translation too. Check
carefully the warnings of the C compiler at the end. I think that MSVC
-is "nice" in the sense that by default a lot of mismatches of integer
-sizes are reported as warnings.
+is lenient in that by default a lot of mismatches of integer sizes are
Then you need to review ``pypy/module/*/`` for ``LONG-versus-Signed``
issues. At some time during this review, we get a working translated
PyPy on Windows 64 that includes all ``--translationmodules``, i.e.
-everything needed to run translations.
When we are th ere, the hacked
+everything needed to run translations. we e th, the hacked
CPython64/64 becomes much less important, because we can run future
translations on top of this translated PyPy. As soon as we get there,
please *distribute* the translated PyPy. It's an essential component