From: Joseph Myers <joseph@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [9/9] Support __float128 format on Intel and Power
Date: Thu, 25 Aug 2016 23:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1608252319100.10074@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20160825150829.9A434C9FB@oc7340732750.ibm.com>
On Thu, 25 Aug 2016, Ulrich Weigand wrote:
> Since at this point we do not yet have any indication in the debug info to
> distinguish different floating-point formats of the same length, we simply
> use the type name as hint. Types named "__float128" get the IEEE format.
Note that now (GCC 7) __float128 is a built-in typedef (i.e. a name
registered with the register_builtin_type langhook) for _Float128, and
_Float128 is the primary name used when the type is created. If I build a
program with GCC 7 that uses __float128, the debug info I get references
_Float128 (and not __float128 as far as I can see).
Obviously debugging should work whether someone uses _Float128 or
__float128 (and in C++, right now they can only use __float128, as the
keyword _Float128 is C-specific). Then on Power, _Float64x is also
binary128 when available (but is a distinct type at the C level from
_Float128), but on x86 it has the Intel extended format (but is a distinct
type from long double).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-08-25 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:08 Ulrich Weigand
2016-08-25 23:28 ` Joseph Myers [this message]
2016-08-26 18:18 ` [9/9 v2] Support 128-bit IEEE floating-point types " Ulrich Weigand
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.1608252319100.10074@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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