This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, mark.dickinson, vstinner
Date 2008-11-05.00:57:48
SpamBayes Score 0.0013772601
Marked as misclassified No
Message-id <1225846670.9.0.0995631982967.issue4258@psf.upfronthosting.co.za>
In-reply-to
Content
oh yay, thanks.  it looks like you did approximately what i had started
working on testing a while back but have gone much further and added
autoconf magic to try and determine when which size should be used.  good.

(i haven't reviewed your autoconf stuff yet)

As for marhsalled data and pyc compatibility, yes that is important to
consider.

We should probably base the decision on which digit size to use
internally on benchmarks, not just if the platform can support 64bit
ints.  Many archs support 64bit numbers as a native C type but require
multiple instructions or are very slow when doing it.

(embedded arm, mips or ppc come to mind as obvious things to test that on)
History
Date User Action Args
2008-11-05 00:57:52gregory.p.smithsetrecipients: + gregory.p.smith, mark.dickinson, vstinner
2008-11-05 00:57:50gregory.p.smithsetmessageid: <1225846670.9.0.0995631982967.issue4258@psf.upfronthosting.co.za>
2008-11-05 00:57:49gregory.p.smithlinkissue4258 messages
2008-11-05 00:57:48gregory.p.smithcreate