From: Segher Boessenkool <segher@kernel.crashing.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Patrick McGehearty <patrick.mcgehearty@oracle.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v3] Fix for powerpc64 long double complex divide failure
Date: Thu, 26 Aug 2021 12:04:42 -0500 [thread overview]
Message-ID: <20210826170442.GG1583@gate.crashing.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2108131701580.20072@digraph.polyomino.org.uk>
Hi!
On Fri, Aug 13, 2021 at 05:12:47PM +0000, Joseph Myers wrote:
> That should be the function __divtc3. (A single libgcc binary supports
> multiple long double formats, so libgcc function names referring to
> floating-point modes need to be understood as actually referring to a
> particular *format*, which may or may not correspond to the named *mode*
> depending on the compilation options used. Thus, libgcc functions with
> "tf" or "tc" in their names, on configurations such as
> powerpc64le-linux-gnu that ever supported IBM long double, always refer to
That is historical as well. Long ago the only 128-bit format was
double-double, and those mode names became part of the symbol names.
Changing this to __divic3 etc. would not really help.
Since the internal GCC symbol names are not really user-visible it does
not matter so much.
Segher
next prev parent reply other threads:[~2021-08-26 17:05 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
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 [this message]
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=20210826170442.GG1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=patrick.mcgehearty@oracle.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).