En/na Tim Hochberg ha escrit:: > Francesc Altet wrote: > [...] >>Uh, I'm afraid that yes. In PyTables, int64, while being a bit bizarre for >>some users (specially in 32-bit platforms), is a type with the same rights >>than the others and we would like to give support for it in numexpr. In fact, >>Ivan Vilata already has implemented this suport in our local copy of numexpr, >>so perhaps (I say perhaps because we are in the middle of a big project now >>and are a bit scarce of time resources) we can provide the patch against the >>latest version of David for your consideration. With this we can solve the >>problem with int64 support in 32-bit platforms (although addmittedly, the VM >>gets a bit more complicated, I really think that this is worth the effort) > > In addition to complexity, I worry that we'll overflow the code cache at > some point and slow everything down. To be honest I have no idea at what > point that is likely to happen, but I know they worry about it with the > Python interpreter mainloop. Also, it becomes much, much slower to > compile past a certain number of case statements under VC7, not sure > why. That's mostly my problem though. > [...]
Hi! For your information, the addition of separate, predictably-sized
int (int32) and long (int64) types to numexpr was roughly as complicated
as the addition of boolean types, so maybe the increase of complexity
isn't that important (but I recognise I don't know the effect on the
final size of the VM).
As soon as I have time (and a SVN version of numexpr which passes the
tests ;) ) I will try to merge back the changes and send a patch to the
list. Thanks for your patience! :)
::
Ivan Vilata i Balaguer >qo< http://www.carabos.com/
Cárabos Coop. V. V V Enjoy Data
""
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
