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 jneb
Recipients jneb, mark.dickinson, serhiy.storchaka, tim.peters
Date 2021-01-15.16:30:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1610728236.86.0.714082152356.issue42911@roundup.psfhosted.org>
In-reply-to
Content
Well, measurements show that it saves more time than I thought (sometimes over 20%!), because there are other ways in which it saves time; I am quite happy with that.

In the code I needed functions _Py_bit_length64 and _Py_bit_count64.
I thought these could better move to the bitutils, but I am not sure about a good name to use, since there are probably other places where these are used, too (I know of at least one in hashtable.c).
The 32 bits versions in bitutils are called _Py_bit_length and _Py_popcount32 (not the most logical names).
So then it would also be more logical to give all four of these consistent names, everywhere. But that's probably better at a later time, right?
History
Date User Action Args
2021-01-15 16:30:36jnebsetrecipients: + jneb, tim.peters, mark.dickinson, serhiy.storchaka
2021-01-15 16:30:36jnebsetmessageid: <1610728236.86.0.714082152356.issue42911@roundup.psfhosted.org>
2021-01-15 16:30:36jneblinkissue42911 messages
2021-01-15 16:30:36jnebcreate