| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14542 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
not encouraged to use it. Punctuation.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14541 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14538 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14537 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
| |
Note: With "icx -O2" (at least), 8 tests are now failing with
Intel(R) oneAPI DPC++ Compiler 2021.2.0 (2021.2.0.20210317).
But no failures when the compiler is invoked as "clang".
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14536 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14535 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14534 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14532 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
| |
in some cases
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14531 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14529 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14528 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14527 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
by a test.
Note that len == 0 is possible when outputting an integer 0 (either a
native one or mpfr_prec_t) with precision field = 0. The consequence
of this bug:
* In debug mode (MPFR_ASSERTD assertion checking), one would get an
assertion failure.
* Otherwise, there should be no side effects since the code was valid
for len == 0, possibly except with LTO (very unlikely, though).
This incorrect assertion was added on 2009-03-13 in r6099.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14521 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
with precision field 0 (also yields a call to buffer_cat with len = 0).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14520 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
from int to void (when the value is never used).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14519 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
conversion specifier.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14518 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
| |
the specification concerning the precision (this was needed because
the conversion specifier 'b' does not exist in C).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14517 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
conversion specifier, which is completely unintuitive. FIXME?
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14516 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14515 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14514 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14513 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14512 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14511 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14510 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
| |
(https://sympa.inria.fr/sympa/arc/mpfr/2021-05/msg00000.html)
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14509 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14508 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14507 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14506 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
| |
for "I" / "i".
* mpfr.texi: added "with the rules of the C locale" in the
mpfr_strtofr description.
* README.dev: completed information about Turkish locales.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14505 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14504 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14503 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
| |
the mpfr_check_range macro).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14502 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14501 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14500 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14499 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14498 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14497 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
| |
Note: the issue (an uninitialized variable) was detected by GCC 6.5.0;
recent GCC versions miss the -Wmaybe-uninitialized warning.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14496 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14495 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14494 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
| |
Note: In these cases, the test should be false if one of the arguments
is NaN (it is not always clear whether NaN is impossible, but just in
case, mpfr_equal_p is safer, in particular if the code around changes;
and this is more readable too).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14493 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14492 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14489 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
|
|
| |
* src/get_str.c: use MPFR_SAVE_EXPO_MARK / MPFR_SAVE_EXPO_FREE to fix
2 issues in mpfr_get_str_ndigits: the inexact flag could be raised
(bug reported by Pierre Chatelier[*]); undefined behavior in a very
reduced exponent range.
* tests/tget_str.c: check the above issues in the tests.
[*] https://sympa.inria.fr/sympa/arc/mpfr/2021-04/msg00000.html
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14488 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
| |
The standard just says that __LINE__ in an integer constant. So its
type might be larger than int, even though the value is representable
in an int (like in MPFR). This concerns logging code, only available
for GCC compatible compilers, so that there should not be any issue
without the cast, but just in case...
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14487 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14485 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
| |
Added m4/ax_pthread.m4 from
https://github.com/autoconf-archive/autoconf-archive
and updated:
* acinclude.m4 (in particular, set CXX and CXXFLAGS)
* doc/README.dev
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14482 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
| |
explicitly, which appears with ax_pthread.m4 29, i.e. with
https://github.com/autoconf-archive/autoconf-archive/commit/2567e0ce0f3a11b535c6b527386197fb49ff172b
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14481 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
| |
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14480 280ebfd0-de03-0410-8827-d642c229c3f4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The AC_HEADER_TIME macro is obsolescent in autoconf 2.69 (2012),
and autoconf 2.71 (2021) outputs a warning, which makes autogen.sh
fail due to "--warnings=all,error", so let's avoid the warnings.
This macro defines TIME_WITH_SYS_TIME, used only in tests/tests.c
(but actually not needed). We actually have two cases:
1. HAVE_GETTIMEOFDAY is defined: we use gettimeofday(), which
needs <sys/time.h>.
2. Otherwise: we use time(), which needs <time.h>.
Based on that, we can simplify the condition in tests/tests.c for
the inclusion of time-related headers, and we no longer need to
check the <sys/time.h> availability. If gettimeofday() is defined
but <sys/time.h> is not available (which shouldn't occur), then
the current gettimeofday() usage may be incorrect anyway.
Changes:
* acinclude.m4:
- no longer use AC_HEADER_TIME;
- no longer check the sys/time.h header.
* tests/tests.c: simplify the inclusion of time-related headers.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14479 280ebfd0-de03-0410-8827-d642c229c3f4
|