This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH to c-commonc.c, preliminary for PR/3865 fix
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 30 Aug 2002 13:18:17 -0700
- Subject: Re: PATCH to c-commonc.c, preliminary for PR/3865 fix
- References: <m3bs7oy7vo.fsf@soliton.integrable-solutions.net>
On Tue, Aug 27, 2002 at 11:21:31AM +0200, Gabriel Dos Reis wrote:
>
> As discussed in the thread starting at
>
> http://gcc.gnu.org/ml/gcc/2002-08/msg01391.html
>
> I'm about to check-in the following patch, a preliminary for fixing
> numerical supports in the C++ runtime system (see for example
> PR/3865).
1) It would be more efficient if you turned most of these into
CPP-level builtin macros -- the values to define them with would
have to be poked into the library at initialization time, but
that could be a structure and a single function call.
2) Why do you have both __TARGET_FLOAT_FORMAT__ and
__TARGET_USES_VAX_*_FLOAT__?
3) Do we _really_ have targets where bit endianness != byte
endianness? I realize they are distinguished at the tm.h level,
but I suspect in practice this does not happen. Same question
about (integer) byte endianness and word endianness; there I know
code exists that blindly assumes the two are the same.
zw