patch for problem when mips16 hard float is linked as c++

[Richard Sandiford]

reed kotler <rkotler at mips.com> writes:
> For mips16 hard float, we are running llvm with soft float "on" in the 
> target independent part of the code.
>
> I would like to revisit some things more at a later time but in
> general the soft float in llvm does not seem to consistently preserve
> the signature information of function calls. It only has enough for
> normal code generation but if some float parameter has been changed to
> integer because it's soft float, I can't always know that anymore.

Ah, OK, thanks.  I can see why that would complicate things.
(GCC also effectively compiles MIPS16 code with soft-float on, but it
keeps the distinction between integer and floating-point throughout.)

Richard