From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: gcc@gcc.gnu.org
Subject: Re: GCC 8.0.0 Status Report (2018-01-15), Trunk in Regression and Documentation fixes only mode
Date: Tue, 06 Feb 2018 16:14:00 -0000 [thread overview]
Message-ID: <20180206161438.GA10578@zira.vinc17.org> (raw)
In-Reply-To: <8441a3a4-de80-cf19-f9fe-2251fb9064e2@ubuntu.com>
On 2018-02-06 10:49:48 +0100, Matthias Klose wrote:
> I have seen some issues with mpfr 4.0.0 on 32bit platforms, however
> not in GCC itself yet. These are all fixed in 4.0.1 rc2, so maybe
> document 4.0.1 instead of 4.0.0 once it is released.
The issues were also present on 64-bit platforms and were due to
a bug in mpfr_div_ui, which has always been present, since 1999.
With MPFR 4.0.0, they are also visible with mpfr_div just because
mpfr_div now uses mpfr_div_ui in some simple cases. I don't think
that GCC could be affected because AFAIK, a failure can only occur
when the input and output precisions are different, or is this
possible with GCC?
Now, I've just found a "regression" when comparing Sipe results with
MPFR results, but it is the Sipe result with SIPE_FLOAT equal to 1
(float) or 2 (double) that is incorrect, 3 (long double) being OK.
Bug triggered with -O2 -march=native on an Intel Xeon E5-2609 v3
machine. At least from 4.9 to 8.0.1 20180124 [trunk revision 257009]
are affected. I'll try to find a simple test case for a bug report.
I suspect that the regression comes from the fact this is a new
machine + the use (as in the past) of -march=native.
--
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)
next prev parent reply other threads:[~2018-02-06 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 8:21 Richard Biener
2018-01-16 12:50 ` Segher Boessenkool
2018-01-16 17:11 ` Joseph Myers
2018-01-17 17:56 ` Segher Boessenkool
2018-01-16 19:20 ` Andrew Roberts
2018-01-17 8:20 ` Richard Biener
2018-01-26 14:22 ` Rainer Orth
2018-01-26 18:56 ` Andrew Roberts
2018-01-27 14:38 ` Rainer Orth
2018-02-06 9:22 ` Rainer Orth
2018-02-06 9:49 ` Matthias Klose
2018-02-06 16:14 ` Vincent Lefevre [this message]
2018-02-06 16:28 ` Vincent Lefevre
2018-02-06 17:34 ` Joseph Myers
2018-02-06 21:59 ` Vincent Lefevre
2018-02-06 17:32 ` Joseph Myers
2018-02-06 21:48 ` Vincent Lefevre
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=20180206161438.GA10578@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).