From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: gcc@gcc.gnu.org
Subject: GNU MPFR 4.1.1 Release Candidate
Date: Thu, 6 Oct 2022 02:34:44 +0200 [thread overview]
Message-ID: <20221006003444.GJ18142@zira.vinc17.org> (raw)
The release of GNU MPFR 4.1.1 ("épinards à la crème", patch level 1)
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.1.1/mpfr-4.1.1-rc1.tar.xz
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.bz2
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.gz
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.zip
The SHA1 digests:
1a01a100d91f91760f116c1f3efb77fc87ebab28 mpfr-4.1.1-rc1.tar.bz2
f8097f9cdd10312a9b554012aec3230bdc719a17 mpfr-4.1.1-rc1.tar.gz
903d59de1b6e08b8570f3673080f8e2a1129c94c mpfr-4.1.1-rc1.tar.xz
a371751f71cef3874c91fdc81b4d41bd61dd0311 mpfr-4.1.1-rc1.zip
The SHA256 digests:
0da78120b10d2f51265fc7da2786f5a8cea960ae2e91e55865a0e7b2a5ab56e4 mpfr-4.1.1-rc1.tar.bz2
ecb2045d9cab07290c02a5a70a37f0be822f679b3ba276628e2a6ba08cf97295 mpfr-4.1.1-rc1.tar.gz
7b78560f8101825fde2ff22cda292917f022c862232da71062307f015f0b3942 mpfr-4.1.1-rc1.tar.xz
d932a61386e2d1e69a1445f6f6794c19e42c6751c3c34845183c408b277a6e21 mpfr-4.1.1-rc1.zip
The signatures:
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.xz.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.bz2.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-rc1.tar.gz.asc
https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1-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 version 4.1.0 to version 4.1.1:
- Bug fixes (see <https://www.mpfr.org/mpfr-4.1.0/#fixed> and/or the
ChangeLog file), in particular for macros implementing functions.
- Improved manual formatting, by using a recent texinfo.tex file.
Please send success and failure reports with "./config.guess" output
to <mpfr@inria.fr>.
If no problems are found, GNU MPFR 4.1.1 should be released
around 2022-10-15.
Note: InriaForge closed last year, so some URLs on the MPFR website
(those at gforge.inria.fr) no longer work. I have converted the links
to commits, as those at <https://www.mpfr.org/mpfr-4.1.0/#fixed>.
I'll try to do additional changes in the next few days.
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-10-06 0:34 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=20221006003444.GJ18142@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).