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 tim.peters
Recipients tim.peters
Date 2022-01-24.18:46:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643049988.78.0.00524175135095.issue46504@roundup.psfhosted.org>
In-reply-to
Content
x_divrem1() was recently (bpo-46406) changed to generate faster code for division, essentially nudging optimizing compilers into recognizing that modern processors compute the quotient and remainder with a single machine instruction.

The same can be done for x_divrem(), although it's less valuable there because the HW division generally accounts for a much smaller percent of its total runtime.

Still, it does cut a multiply and subtract out of the loop, and makes the code more obvious (since it brings x_divrem1() and x_divrem() back into synch).
History
Date User Action Args
2022-01-24 18:46:28tim.peterssetrecipients: + tim.peters
2022-01-24 18:46:28tim.peterssetmessageid: <1643049988.78.0.00524175135095.issue46504@roundup.psfhosted.org>
2022-01-24 18:46:28tim.peterslinkissue46504 messages
2022-01-24 18:46:28tim.peterscreate