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 mark.dickinson
Recipients flox, mark.dickinson, r.david.murray, theller
Date 2010-04-07.09:43:56
SpamBayes Score 1.1215853e-06
Marked as misclassified No
Message-id <1270633438.69.0.610352349547.issue8314@psf.upfronthosting.co.za>
In-reply-to
Content
It's surprising that test_ulonglong fails, while test_longlong passes:  can the Linux Sparc ABI really be treating these two types differently?

Maybe more information could be gained by supplying a more interesting test value than 42---some 8-byte value with all bytes different, for example.

In any case, this seems likely to be a libffi bug somewhere;  maybe we could bring it up on the libffi mailing list.  If we can translate the failing Python code into failing C code first that would probably increase the chances of getting a good answer.  Without access to Sparc hardware, I don't see much other way of making progress here.
History
Date User Action Args
2010-04-07 09:43:58mark.dickinsonsetrecipients: + mark.dickinson, theller, r.david.murray, flox
2010-04-07 09:43:58mark.dickinsonsetmessageid: <1270633438.69.0.610352349547.issue8314@psf.upfronthosting.co.za>
2010-04-07 09:43:57mark.dickinsonlinkissue8314 messages
2010-04-07 09:43:56mark.dickinsoncreate