lp:mpfr

Created by DNS on 2011-10-16 and last modified on 2019-04-16
Get this branch:
bzr branch lp:mpfr

Related bugs

Related blueprints

Branch information

Owner:
RBOSE VCS Imports
Project:
mpfr
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the Subversion branch from svn://scm.gforge.inria.fr/svn/mpfr/trunk.

The next import is scheduled to run in 3 hours.

Last successful import was 2 hours ago.

Import started 2 hours ago on izar and finished 2 hours ago taking 25 seconds — see the log
Import started 8 hours ago on alnitak and finished 8 hours ago taking 20 seconds — see the log
Import started 14 hours ago on izar and finished 14 hours ago taking 25 seconds — see the log
Import started 20 hours ago on izar and finished 20 hours ago taking 20 seconds — see the log
Import started on 2019-04-18 on alnitak and finished on 2019-04-18 taking 20 seconds — see the log
Import started on 2019-04-18 on alnitak and finished on 2019-04-18 taking 25 seconds — see the log
Import started on 2019-04-18 on izar and finished on 2019-04-18 taking 20 seconds — see the log
Import started on 2019-04-18 on izar and finished on 2019-04-18 taking 25 seconds — see the log
Import started on 2019-04-17 on izar and finished on 2019-04-17 taking 20 seconds — see the log
Import started on 2019-04-17 on alnitak and finished on 2019-04-17 taking 25 seconds — see the log

Recent revisions

10712. By vlefevre on 2019-04-16

New macro MPFR_FALLTHROUGH to avoid -Wimplicit-fallthrough warnings
with GCC 7+. This macro also makes the code more readable by bringing
the attention on an unusual fallthrough in a switch case.
  * src/mpfr-impl.h: define this macro.
  * src/vasprintf.c: use this macro in a case of fallthrough.

10711. By vlefevre on 2019-04-15

[src/vasprintf.c] Minor bug fix: when an integer is to be read for
  the field width or precision, regard strings like "17*" as invalid
  instead of regarding it as "*" (ignoring the integer that precedes,
  except in case of overflow). In C's printf, such an invalid string
  yields undefined behavior, but in MPFR, we normally print the
  invalid format specifier as a literal string in such a case.
  Bug detected with -Wimplicit-fallthrough from GCC 7+.
[tests/tsprintf.c] Added non-regression test.

10710. By vlefevre on 2019-04-02

[configure.ac] Updated --enable-logging description.

10709. By vlefevre on 2019-04-02

[acinclude.m4] When logging support is requested, run a test for
nested functions and 'cleanup' attribute, which are needed.

10708. By vlefevre on 2019-04-02

[configure.ac] AC_ARG_ENABLE(float128,...): updated comment and
description.

10707. By vlefevre on 2019-04-02

[configure.ac] Updated comment for AC_ARG_ENABLE(decimal-float,...).
  * Removed information about very old GCC versions.
  * _Decimal128 is considered too, in addition to _Decimal64.
  * No longer just a GCC extension, but part of ISO/IEC TS 18661.
  * Added a FIXME for new options about _Decimal64 and _Decimal128.

10706. By vlefevre on 2019-04-02

[configure.ac] Cleanup: moved some AC_ARG_ENABLE's where they should be.

10705. By vlefevre on 2019-03-29

[src/vasprintf.c]
  * Corrected FIXME by modifying the assertion. The failure could occur
    only when mpfr_intmax_t has the same size of int (which is the case
    when long = int and either intmax_t and long long are not available
    or intmax_t = long = int), and only when INT_MIN is provided as a
    field width argument.
  * Related to that, updated a test to improve optimization.
  * Added comments.

10704. By vlefevre on 2019-03-29

[src/vasprintf.c] Added a FIXME: tsprintf yields an assertion failure
with sizeof(mpfr_intmax_t) = 4 (which was not tested until now).

10703. By vlefevre on 2019-03-29

Cleanup / fixes related to intmax_t, mpfr_intmax_t, etc.

The issues were:
  * The build of the tests (make check) could fail with CFLAGS implying
    "-std=c90 -Werror=format", i.e. if intmax_t was available but the
    use of the "j" printf length modifier made the compilation fail
    (its unconditional use was incorrect anyway).
  * MPFR_INTMAX_MAX had definitions in both mpfr-impl.h & mpfr-intmax.h,
    with inconsistent usage.

Detailed changes:
  * acinclude.m4: removed the definition of MPFR_PRINTF_MAXLM, which
    could be incorrect (large numbers were not tested to select its
    value); in the MPFR_FUNC_GMP_PRINTF_SPEC macro, check sprintf()
    in addition to gmp_sprintf() as it is now also used in the tests;
    updated some comments and messages.
  * src/mpfr-impl.h: removed the MPFR_*INTMAX* definitions; they had
    been added due to
      https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582698
    with -ansi -pedantic-errors, but this issue was fixed in GCC 4.8
    (released 6 years ago), so that they are no longer needed.
  * src/mpfr-intmax.h: completed the definitions; mpfr_intmax_t is now
    the largest integer type available and fully working (in particular
    with printf), thus it may be smaller than intmax_t.
  * doc/README.dev: updated the description of mpfr_intmax_t, etc.
  * tests/tversion.c: output sizeof(mpfr_intmax_t) too.
  * Various .c files in src and tests related to (u)intmax_t: use
    INTMAX_MAX instead of MPFR_INTMAX_MAX, etc. as Debian bug 582698
    (mentioned above) no longer occurs and mpfr_intmax_t may be smaller
    than intmax_t; use the "j" printf length modifier instead of
    MPFR_PRINTF_MAXLM, and protect it with "#ifndef NPRINTF_J"
    (only the tests are concerned, so that this is not an issue).

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.