This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Two or three initial observations on the fp prining patch
Gabriel Dos Reis wrote:
Paolo Carlini <pcarlini@unitus.it> writes:
| Basically, we get *all* the information we need for floatconv.cc!
Yes. And that is one reason I would recommand against duplicating
codes. Built-in macros come to mind.
I'm not sure to understand what you are suggesting, in the sense that
I don't think we currently have available built-in macros for what we
need. I know what you mean about the work encouraged by Benjamin,
something like:
2002-08-27 Gabriel Dos Reis <gdr@integrable-solutions.net>
* c-common.c (cpp_define_data_format): New function.
(cb_register_builtins): Call it.
* doc/cpp.texi (Common Predefined Macros): Document
__TARGET_BITS_ORDER__, __TARGET_BYTES_ORDER__,
__TARGET_INT_WORDS_ORDER__, __TARGET_FLOAT_WORDS_ORDER__,
__TARGET_FLOAT_FORMAT__, __TARGET_USES_VAX_F_FLOAT__,
__TARGET_USES_VAX_D_FLOAT__, __TARGET_USES_VAX_G_FLOAT__,
__TARGET_USES_VAX_H_FLOAT__.
but then:
2002-09-21 Richard Henderson <rth@redhat.com>
* c-common.c (cpp_define_data_format): Remove __GCC_LITTLE_ENDIAN__,
__GCC_BIG_ENDIAN__, __TARGET_BITS_ORDER__, __TARGET_BYTES_ORDER__,
__TARGET_INT_WORDS_ORDER__, __TARGET_FLOAT_WORDS_ORDER__,
__TARGET_USES_VAX_F_FLOAT__, __TARGET_USES_VAX_D_FLOAT__,
__TARGET_USES_VAX_G_FLOAT__, __TARGET_USES_VAX_H_FLOAT__.
* doc/cpp.texi: Don't document them.
So, where is *now* __TARGET_FLOAT_WORDS_ORDER_?
Are you suggesting to re-add you patch?
Paolo.