➜

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 fil
Recipients alex, fil, francismb, mark.dickinson, meador.inge, pitrou, skrah, tim.peters
Date 2013-12-09.00:39:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386549565.71.0.377815756724.issue19904@psf.upfronthosting.co.za>
In-reply-to
Content 
Antoine,

No, the SIMD vector should be treated as a int128 (for eg.), not as 4 python ints. It is the unpacking process that unpacks into 4 python ints. The two shouldn't be confused - you definitely want to be able to treat the vector in both states (packed and unpacked).

I'm not saying that Python should necessarily make use of SIMD instructions (don't think performance is critical there in py), but that it should at least be access to a raw 128/256/512 bit integer within a C structure. Part of this is interacting with SIMD'able structures - at least in my use cases :)
History
Date User Action Args
2013-12-09 00:39:25filsetrecipients: + fil, tim.peters, mark.dickinson, pitrou, alex, skrah, meador.inge, francismb
2013-12-09 00:39:25filsetmessageid: <1386549565.71.0.377815756724.issue19904@psf.upfronthosting.co.za>
2013-12-09 00:39:25fillinkissue19904 messages
2013-12-09 00:39:25filcreate