From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: gcc@gcc.gnu.org
Subject: GNU MPFR 4.2.0 Release Candidate
Date: Tue, 13 Dec 2022 16:53:20 +0100 [thread overview]
Message-ID: <20221213155320.GI7634@zira.vinc17.org> (raw)
The release of GNU MPFR 4.2.0 ("fondue savoyarde") is imminent.
Please help to make this release as good as possible by downloading
and testing this release candidate:
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.xz
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.bz2
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.gz
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.zip
The SHA1 digests:
72b03404b996494c79c13060fea6c9df68d4d99d mpfr-4.2.0-rc1.tar.bz2
6123e3495501f3d1f45368cf85dcab18fc6e9784 mpfr-4.2.0-rc1.tar.gz
00fa7c1ec1c5dd23cea3692b5351ab4e81e8ca27 mpfr-4.2.0-rc1.tar.xz
7f8e17d2c71e45fdba0d0547db68e8d37c8ad077 mpfr-4.2.0-rc1.zip
The SHA256 digests:
acb9c23e84ba946e974ef21c2afb8c6dd8017cdeb199f61741123f5393b150b8 mpfr-4.2.0-rc1.tar.bz2
50e34f8c7835c8fe66d7aa16d0f9b9c354df6bfb0d4ead780263f0a39ff14d8f mpfr-4.2.0-rc1.tar.gz
1f89ef8631753c50118ec5273ab2fd0d70fbb0e6f33c36a6b673e7e8c51cf5ef mpfr-4.2.0-rc1.tar.xz
eb0de4bdbcb9b8b2b28b130aa053e3ad105ceed3ae0392c5911119b149a07b20 mpfr-4.2.0-rc1.zip
The signatures:
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.xz.asc
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.bz2.asc
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.tar.gz.asc
https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0-rc1.zip.asc
Each tarball is signed by Vincent Lefèvre. This can be verified using
the GPG key ID 5831D11A0D4DB02A; this key can be retrieved with:
gpg --recv-keys 5831D11A0D4DB02A
or by downloading it from <https://www.vinc17.net/pgp.html>.
The key fingerprint is:
A534 BE3F 83E2 41D9 1828 0AEB 5831 D11A 0D4D B02A
The signatures can be verified with: gpg --verify <file.asc>
You should check that the key fingerprint matches.
Changes from versions 4.1.* to version 4.2.0:
- The "fondue savoyarde" release.
- Binary compatible with MPFR 4.0.* and 4.1.*, though some minor changes in
the behavior of the formatted output functions may be visible, regarded
as underspecified behavior or bug fixes (see below).
- New functions mpfr_cosu, mpfr_sinu, mpfr_tanu, mpfr_acosu, mpfr_asinu,
mpfr_atanu and mpfr_atan2u.
- New functions mpfr_cospi, mpfr_sinpi, mpfr_tanpi, mpfr_acospi, mpfr_asinpi,
mpfr_atanpi and mpfr_atan2pi.
- New functions mpfr_log2p1, mpfr_log10p1, mpfr_exp2m1, mpfr_exp10m1 and
mpfr_compound_si.
- New functions mpfr_fmod_ui, mpfr_powr, mpfr_pown, mpfr_pow_uj, mpfr_pow_sj
and mpfr_rootn_si (mpfr_pown is actually a macro defined as an alias for
mpfr_pow_sj).
- Bug fixes.
In particular, for the formatted output functions (mpfr_printf, etc.),
the case where the precision consists only of a period has been fixed
to be like ".0" as specified in the ISO C standard, and the manual has
been corrected and clarified.
The macros of the custom interface have also been fixed: they now behave
like functions (except a minor limitation for mpfr_custom_init_set).
Please send success and failure reports with "./config.guess" output
to <mpfr@inria.fr>.
If no problems are found, GNU MPFR 4.2.0 should be released
around 2022-12-25.
Regards,
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
reply other threads:[~2022-12-13 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221213155320.GI7634@zira.vinc17.org \
--to=vincent+gcc@vinc17.org \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).