cpython

Commit Graph

Author	SHA1	Message	Date
Stefan Krah	6e467049c6	Accept Unicode legacy strings in the Decimal constructor.	13 years ago
Stefan Krah	0f82b76b57	Issue #16431 : Finally, consider all permutations.	13 years ago
Stefan Krah	ed16eff57e	Issue #16431 : Also fix the opposite direction.	13 years ago
Stefan Krah	f4abc7b8a0	Issue #16431 : Use the type information when constructing a Decimal subtype from a Decimal argument.	13 years ago
Stefan Krah	a0346e56ac	Support gcc's -ansi flag: use "__asm__" instead of "asm".	13 years ago
Stefan Krah	e59aa8c94d	Revert 29506c7db353 (build output should be accurate).	13 years ago
Christian Heimes	72c9946718	Change libmpdec to use ANSI code in strict ansi mode as inline asm isn't supported in ANSI C	13 years ago
Stefan Krah	9a3f05e60f	Make it clear that the pi function is modified for benchmarking purposes.	13 years ago
Stefan Krah	6b6a1df996	Restore the benchmark order to avoid waiting for decimal.py if just the prec=9 test is used.	13 years ago
Brett Cannon	6cf50c5b1d	Fix whitespace.	13 years ago
Brett Cannon	63092fe0ea	Fix whitespace.	13 years ago
Brett Cannon	d266c4451f	Make the decimal bench file run under Python 2.7.	13 years ago
Stefan Krah	7e6523fbd7	Use C-style comments.	13 years ago
Stefan Krah	f817a7b178	Use C-style comments.	13 years ago
Stefan Krah	76e12179c5	Issue #15882 : Change _decimal to accept any coefficient tuple when constructing infinities. This is done for backwards compatibility with decimal.py: Infinity coefficients are undefined in _decimal (in accordance with the specification).	14 years ago
Stefan Krah	dbcf103be0	Issue #15882 : Change _decimal to accept any coefficient tuple when constructing infinities. This is done for backwards compatibility with decimal.py: Infinity coefficients are undefined in _decimal (in accordance with the specification).	14 years ago
Mark Dickinson	fc33d4ce0a	Issue #15544 : Fix Decimal.__float__ to work with payload-carrying NaNs.	14 years ago
Stefan Krah	f21587e3a8	mpd_qpowmod(): calculate result with zero-exponent for compatibility with decimal.py. The hack to remove the ideal exponent is no longer required.	14 years ago
Stefan Krah	17183a2972	Use zero bottom margin.	14 years ago
Stefan Krah	ad5b43995e	In the 32-bit build, dec_hash() raised InvalidOperation if the operand had a coefficient with MAX_PREC=425000000 digits and a negative exponent. Increasing the context limits above the official values fixes the issue and is safe (in this case!).	14 years ago
Stefan Krah	2fd502f6a1	1) Use _mpd_basedivmod() regardless of the length of the dividend. This is required for a corner case in dec_hash() in the following commit and also usually faster. dec_hash() needs some extra precision above MPD_MAX_PREC, and _mpd_base_ndivmod() is not audited for that. 2) Use _mpd_basemul() if the length of the smaller operand is less than or equal to 256. While this is technically an optimization, it is required for testing corner cases in dec_hash() in reasonable time.	14 years ago
Stefan Krah	b9e36b97f2	Add unused parameter to a couple of METH_NOARGS functions. The previous form is used in many places in the source tree, but was found to be incorrect in a recent tracker discussion.	14 years ago
Stefan Krah	26a1c7a905	Fix Visual Studio warning.	14 years ago
Stefan Krah	e574402bd6	Issue #7652 : Clean up _mpd_qinvroot() and mark it LIBMPDEC_ONLY. Use the algorithm from decimal.py for mpd_qsqrt().	14 years ago
Stefan Krah	d57caf36bd	Remove ISSUES.txt.	14 years ago
Stefan Krah	5431e30853	After 79d2eb29c755 it is no longer necessary to zero the output array: None of the _mpd_shortadd() or _mpd_shortmul() functions read uninitialized values. Previously zeroing was required since _mpd_real_size() was called on the output array.	14 years ago
Stefan Krah	c35a8e5c98	Proactive reliability fix for broken FPUs: The base conversion functions use log10() to calculate the size of the output array. The current code has been tested on x86/amd64 (and to a lesser extent on qemu-mips qemu-sparc) and produces sufficiently large values for all inputs tested so far (coefficient sizes of 10**18 - 1 are hard to test exhaustively). The new code does not rely on the correctness of log10() and resizes the output arrays if the allocated space is insufficient.	14 years ago
Stefan Krah	1edab78859	Update test script to Visual Studio 2010.	14 years ago
Stefan Krah	39e810eb6c	Make the benchmark more fair for _decimal/decimal.py by setting context.prec only once (float obviously doesn't set any context at all).	14 years ago
Stefan Krah	78f075636c	Speed up _decimal by another 10-15% by caching the thread local context that was last accessed. In the pi benchmark (64-bit platform, prec=9), _decimal is now only 1.5x slower than float.	14 years ago
Stefan Krah	3077ab8237	Whitespace.	14 years ago
Stefan Krah	50b0a365ba	Fix comment.	14 years ago
Stefan Krah	22385011ed	Many cleanups of redundant code in mpd_qrem_near(): 1) _mpd_qdivmod() uses the context precision only in two places, and the new code should be exactly equivalent to the previous code. 2) Remove misleading comment. 3) The quotient is an integer with exponent 0, so calling mpd_qtrunc() is pointless. 4) Replace two instances of identical code by a single one. 5) Use _mpd_cmp_abs() instead of mpd_cmp_total_mag(): the operands are not special. 6) Don't clear MPD_Rounded in the status (with the current code it should not be set within the function).	14 years ago
Stefan Krah	9c1feb88f3	Add comments to the power functions, in particular to _mpd_qpow_real().	14 years ago
Stefan Krah	c62bd13cb2	1) State the relative errors of the power functions for integer exponents. 2) _mpd_qpow_mpd(): Abort the loop for all specials, not only infinity. 3) _mpd_qpow_mpd(): Make the function more general and distinguish between zero clamping and folding down the exponent. The latter case is currently handled by setting context->clamp to 0 before calling the function. 4) _mpd_qpow_int(): Add one to the work precision in case of a negative exponent. This is to get the same relative error (0.1 * 10*-prec) for both positive and negative exponents. The previous relative error for negative exponents was (0.2 10**-prec). Both errors are _before_ the final rounding to the context precision.	14 years ago
Stefan Krah	b7832939c7	1) Fix signature of _mpd_qpow_uint(): contrary to the comment base is constant. 2) Abort the loop for all specials, not only infinity. 3) Make the function more general and distinguish between zero clamping and folding down the exponent. The latter case is currently handled by setting context->clamp to 0 before calling the function.	14 years ago
Stefan Krah	88e19779ad	1) Replace long-winded abort() construct by assert(). 2) Remove micro optimization (inline checking for NaN before calling mpd_qcheck_nans()) that probably has no benefit in this case.	14 years ago
Stefan Krah	9253862f45	1) State restrictions for the transform length. 2) Switch argument order to match the function signature of mpd_calloc() (cosmetic change, since the order is irrelevant).	14 years ago
Stefan Krah	afc0c77b42	Add one extra comparison to the _mpd_shortmul() case to avoid repetitive code.	14 years ago
Stefan Krah	5248a2d3c1	Enumerate all cases in the overflow detection strategy in mpd_qlog10().	14 years ago
Stefan Krah	1cf6dfc8b2	1) List relative error for _mpd_qln10(). 2) Add rigorous error analysis to _mpd_qlog10 (ACL2 proofs exist). 3) Use the relative error as a basis for the interval generation in the correction loop (same as in _mpd_qln()).	14 years ago
Stefan Krah	7bda265662	1) The overflow detection in mpd_qln() has a surprising number of case splits. List all of them in the comment. 2) Use the recently stated relative error of _mpd_qln() to generate the interval for the exact value of ln(x). See also the comment in mpd_qexp().	14 years ago
Stefan Krah	a3394bce33	1) Add error analysis comments to mpd_qln10() and _mpd_qln(). 2) Simplify the precision adjustment code for values in [0.900, 1.15].	14 years ago
Stefan Krah	67ee1d05dd	word.digits are always initialized before use in the Taylor series loop, but this is more readable.	14 years ago
Stefan Krah	0271766c88	Use workctx instead of ctx for cosmetic reasons. Also zero-pad the result in the simple path (not correctly rounded but faster).	14 years ago
Stefan Krah	4d3e0a695a	Improve Underflow handling in the correct-rounding loop. The case for Underflow to zero hasn't changed: _mpd_qexp() internally uses MIN_EMIN, so the result would also underflow to zero for all emin > MIN_EMIN. In case digits are left, the informal argument is as follows: Underflow can occur only once in the last multiplication of the power stage (in the Horner stage Underflow provably cannot occur, and if Underflow occurred twice in the power stage, the result would underflow to zero on the second occasion). Since there is no double rounding during Underflow, the effective work precision is now 1 <= result->digits < prec. It can be shown by a somewhat tedious argument that abs(result - ex) < ulp(result, result->digits). Therefore the correct rounding loop now uses ulp(result, result->digits) to generate the bounds for ex in case of Underflow.	14 years ago
Stefan Krah	9a5beece1b	Improve comments.	14 years ago
Stefan Krah	5ddbcfc53e	Pad the result with zeros just before the final rounding.	14 years ago
Stefan Krah	30c35e8154	Do not clobber existing flags.	14 years ago
Stefan Krah	e34a209584	Fix Visual Studio warning.	14 years ago

1 2

82 Commits (c2176e46d797c8aea60cdcd2ddf44f6bb88394b4)