Re: PATCH to c-commonc.c, preliminary for PR/3865 fix

[Paul Koning <pkoning at equallogic dot com>]

>>>>> "Zack" == Zack Weinberg <zack@codesourcery.com> writes:

 Zack> 2) Why do you have both __TARGET_FLOAT_FORMAT__ and
 Zack> __TARGET_USES_VAX_*_FLOAT__?

VAX has G or D float for "double" depending on a compile time switch;
I'd assume that one or the other would be defined to match.

 Zack> 3) Do we _really_ have targets where bit endianness != byte
 Zack> endianness?  I realize they are distinguished at the tm.h
 Zack> level, but I suspect in practice this does not happen.  Same
 Zack> question about (integer) byte endianness and word endianness;
 Zack> there I know code exists that blindly assumes the two are the
 Zack> same.

Well, if by "word" you mean 32 bit datum -- there's the odd PDP11
case, with high order halfword first but low order byte first in the
halfword. 

	  paul