bpo-46311: Clean up PyLong_FromLong and PyLong_FromLongLong#30496
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #27832 inadvertently introduced a couple of changes to
PyLong_FromLongthat didn't make a lot of sense: an(unsigned long)cast was replaced with(twodigits), and a digit count variable (counting number of PyLong digits in a C long) had its type needlessly changed frominttoPy_ssize_t.(unsigned long)cast is obviously correct, while figuring out whether(twodigits)loses information takes some work.long.This PR:
ival < 0 ? 0U-(unsigned long)ival : ival) gets compiled to something branchless on most platforms, as doesival < 0 ? -ndigits : ndigitsPyLong_FromLongLong, which now has a fast path for medium-size values.https://bugs.python.org/issue46311