From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: <libc-alpha@sourceware.org>, <meissner@linux.ibm.com>
Subject: Re: [PATCH] powerpc: Fix the compiler mode used with C++ when -mabi=ieeelongdouble
Date: Fri, 27 Apr 2018 19:32:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1804271917270.29138@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180427171150.28010-1-tuliom@linux.ibm.com>
On Fri, 27 Apr 2018, Tulio Magno Quites Machado Filho wrote:
> When compiling C++ code with -mabi=ieeelongdouble, KCtype is
> unavailable and TCtype should be used instead.
In that case (-mabi=ieeelongdouble), I'd expect you to use "typedef long
double _Float128;" for C++, and _Complex long double as the definition of
__CFLOAT128 for C++, and x##l as the definition of __f128 for C++, as it's
essentially the case implemented by
sysdeps/ieee754/ldbl-128/bits/floatn.h. You shouldn't need to use mode
attributes at all.
(Uses of __HAVE_DISTINCT_FLOAT128 and __HAVE_FLOAT64X_LONG_DOUBLE will
need careful review to see if additional macros are needed to cover this
-mabi=ieeelongdouble case, but the general rule is that they relate to the
*default* long double type for that glibc binary - meaning the one with
__*l symbols, as selection of such implementation-namespace one-per-format
symbols is generally what they are used for in installed headers - meaning
the existing definitions for powerpc remain correct even with
-mabi=ieeelongdouble and you should not copy the
sysdeps/ieee754/ldbl-128/bits/floatn.h definitions of those macros.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-04-27 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 17:12 Tulio Magno Quites Machado Filho
2018-04-27 19:32 ` Joseph Myers [this message]
2018-04-30 14:02 ` Tulio Magno Quites Machado Filho
2018-04-30 14:05 ` Tulio Magno Quites Machado Filho
2018-04-30 14:52 ` Joseph Myers
2018-05-04 20:21 ` Tulio Magno Quites Machado Filho
2018-05-04 21:06 ` Joseph Myers
2018-05-11 19:25 ` [PATCHv2] powerpc: Fix the compiler type " Tulio Magno Quites Machado Filho
2018-05-11 19:56 ` Joseph Myers
2018-05-11 23:23 ` Tulio Magno Quites Machado Filho
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.20.1804271917270.29138@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=meissner@linux.ibm.com \
--cc=tuliom@linux.ibm.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).