Amaury wrote:
>Surely we could have another copy with the largeadressaware flag?
I agree. That's a smart way to proceed for now.
I'm still wondering if there is any technical reason against the flag?
Particularly the "CFFI extensions want the high bit reserved or not" issue.
Matt wrote:
>The port is complicated since on windows 64 bit,/longs/are only 32 bit.
This is a problem for/PyPy/right now, since it assumes that a c/long/can
hold a pointer
I don't want to talk much about a win 64 bit version in this thread because
it's a separate and larger issue. But I am happy to talk about it in a
separate thread or off list. I don't think people outside the core pypy
developers have any idea what the issues really are, and there's no place to
learn them. For instance, why don't solutions for other projects work for
pypy? Is the problem with C code or with RPython code that generates C code?
Can you show an example problem from the source tree? What does the fix for it
look like? How do we find all the places needing a fix? I am happy to work
with someone who knows to document all this. No one will work on the project
without this kind of information, because they don't know what they're signing
up for.
Thanks,
-Roger
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
