Re: cross-compiled floating point constants broken

[Jeffrey A Law <law at hurl dot cygnus dot com>]

  In message <Pine.LNX.4.05.9902031149440.30176-100000@moshier.ne.mediaone.net>
you write:
  > The ASM_OUTPUT_ macros print a host computer `long' or an array of
  > host computer longs.  The purpose of REAL_VALUE_TO_TARGET_DOUBLE, etc.
  > is to set up those longs.  It is solely to make the host computer's
  > printf happy.
Even when doing assembly output you have to be careful about signedness.

Though typically sign extending constants for assembly output is buried in
the target files instead of infecting other parts of the compiler with
such issues.


  > Elsewhere the treatment of integer versus floating values does not
  > seem so clear-cut.  For example, in split_double the pieces get sign
  > extended if the input is an integer type but not if it is a floating
  > point type.  Do we know offhand if that is good or bad?
That sounds like the correct behavior.

jeff