From: Joseph Myers <joseph@codesourcery.com>
To: Patrick McGehearty <patrick.mcgehearty@oracle.com>
Cc: <gcc-patches@gcc.gnu.org>, <segher@kernel.crashing.org>
Subject: Re: [PATCH v3] Fix for powerpc64 long double complex divide failure
Date: Thu, 12 Aug 2021 16:19:35 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2108121616290.2672396@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1628784193-9675-1-git-send-email-patrick.mcgehearty@oracle.com>
On Thu, 12 Aug 2021, Patrick McGehearty via Gcc-patches wrote:
> This patch resolves the failure of powerpc64 long double complex divide
> in native ibm long double format after the patch "Practical improvement
> to libgcc complex divide".
This description is not consistent with the patch.
__divkc3 should always be using IEEE binary128 format, not IBM long
double. If this code is being built for IBM long double, something is
wrong somewhere else.
Using the DFmode values probably makes sense for IBM long double, but not
for IEEE binary128.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-08-12 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 16:03 Patrick McGehearty
2021-08-12 16:19 ` Joseph Myers [this message]
2021-08-12 16:40 ` Patrick McGehearty
2021-08-12 16:47 ` Joseph Myers
2021-08-12 20:53 ` Segher Boessenkool
2021-08-12 22:17 ` Patrick McGehearty
2021-08-13 17:12 ` Joseph Myers
2021-08-26 15:51 ` Patrick McGehearty
2021-08-26 16:34 ` Joseph Myers
2021-08-26 16:57 ` Segher Boessenkool
2021-08-26 17:04 ` Segher Boessenkool
2021-08-12 20:55 ` Segher Boessenkool
2021-08-12 22:36 ` Andreas Schwab
2021-08-13 17:22 ` Joseph Myers
2021-08-27 2:10 ` Michael Meissner
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=alpine.DEB.2.22.394.2108121616290.2672396@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=patrick.mcgehearty@oracle.com \
--cc=segher@kernel.crashing.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).