This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc/libstdc++-v3 ChangeLog configure.target co ...
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Richard dot Earnshaw at arm dot com
- Cc: rearnsha at gcc dot gnu dot org, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: 29 Aug 2002 12:06:18 +0200
- Subject: Re: gcc/libstdc++-v3 ChangeLog configure.target co ...
- Organization: Integrable Solutions
- References: <200208290948.KAA07960@cam-mail2.cambridge.arm.com>
Richard Earnshaw <rearnsha@arm.com> writes:
| > | Log message:
| > | * config/cpu/arm/cpu_limits.h: New file.
| > | * configure.target: Use config/cpu/arm for XScale and StrongARM
| > | configurations.
| >
| > Hi Richard,
| >
| > We're no longer using __glibcpp_long_double_bits in C++'s <limits>.
| > We're getting that info from the compiler through __LONG_DOUBLE_BIT__.
|
| Argh! Extended build cycle times...
I'm sorry about that. Now, the libary view matches that of the
compiler.
| > However, what would be helpful is means to know whether a floating
| > point type uses a hidden bit. For a 32-bit or 64-bit wide
| > floating-point type, that is a non-issue. However, practice varies
| > greatly for the extended floating-point types.
|
| The ARM ABI doesn't use an extended type for long double, it maps directly
| onto double. That is
|
| long double === double
Thanks a lot.
-- Gaby