From: Bernd Schmidt <bschmidt@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: Correct libgcc complex multiply excess precision handling
Date: Wed, 07 Sep 2016 23:01:00 -0000 [thread overview]
Message-ID: <cbc5a372-897f-ed42-7355-14dd7a34fddc@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609072145040.15261@digraph.polyomino.org.uk>
On 09/07/2016 11:48 PM, Joseph Myers wrote:
> libgcc complex multiply is meant to eliminate excess
> precision from certain internal values by forcing them to memory in
> exactly those cases where the type has excess precision. But in
> https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01894.html I
> accidentally inverted the logic so that values get forced to memory in
> exactly the cases where it's not needed. (This is a pessimization in
> the no-excess-precision case, in principle could lead to bad results
> depending on code generation in the excess-precision case. Note: I do
> not have a test demonstrating bad results.)
Ok.
Bernd
prev parent reply other threads:[~2016-09-07 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 23:00 Joseph Myers
2016-09-07 23:01 ` Bernd Schmidt [this message]
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=cbc5a372-897f-ed42-7355-14dd7a34fddc@redhat.com \
--to=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).