From: Michael Veksler <mveksler@tx.technion.ac.il>
To: gcc-help@gcc.gnu.org
Subject: sizeof(long double) vs. std::numeric_limits and x86-64 vs x86
Date: Tue, 27 Sep 2011 05:09:00 -0000 [thread overview]
Message-ID: <4E80F88F.2050608@tx.technion.ac.il> (raw)
Hello,
I wanted to check how many bits long double takes. So I checked
sizeof(long double) which, naturally, may account for padding. On x86-64
it takes 16 bytes and only 12 on x86, a difference of 4 bytes. This
supported my hope that on x86-64 we would have "long double"= |__float128|.
But this difference does not exist in std::numeric_limits<long double>.
Does it really mean that only the
padding is different between the architectures, but the type is still
the same?
If "long double" != |__float128|, then is there any chance to have a
correct definition of std::numeric_limits<__float128> in the near
future? If not, where can I find macro names such as __LDBL_MANT_DIG__
for __float128?
Running
gcc -g -E -dM t.cpp | grep MANT_DIG__
gives only
#define __FLT_MANT_DIG__ 24
#define __DEC64_MANT_DIG__ 16
#define __LDBL_MANT_DIG__ 64
#define __DBL_MANT_DIG__ 53
#define __DEC32_MANT_DIG__ 7
#define __DEC128_MANT_DIG__ 34
no mention of anything like FLT128
Thanks
--
Michael
next reply other threads:[~2011-09-26 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 5:09 Michael Veksler [this message]
2011-09-27 5:12 ` Ian Lance Taylor
2011-09-27 18:27 ` Michael Veksler
2011-09-28 0:41 ` Toon Moene
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=4E80F88F.2050608@tx.technion.ac.il \
--to=mveksler@tx.technion.ac.il \
--cc=gcc-help@gcc.gnu.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).