Re: MIPS64 soft-float: missing definition for __floatdidf and friends

[Roger Sayle <roger at eyesopen dot com>]

Hi Mark,

On Sun, 14 May 2006, Mark Mitchell wrote:
> I think that the current libgcc organization suffers from the faults you
> (Roger) have noted; the way the include files and such are set up seems
> needlessly baroque.  However, I think it's also reasonable to say we
> should avoid duplicating code.  So, I'd suggest that we look for a
> middle path, perhaps along the lines that GLIBC uses for soft-fp, where
> macros are combined in various ways, or, as previously suggested, in
> which a single file is compiled multiple times with different macro
> definitions.

Excellent, I think that we're on exactly the same page.  The libgcc
library needs a simplified build system and probably should be moved
to the  top-level with the minimum amount of unnecessary code duplication.

Pragmatically, the more immediately pressing issue is what to do about
the MIPS64 -msoft-float regressions during the 4.2 timeframe, i.e.
during stage3.

My personal preference of only affecting the MIPS64 targets whilst
continuing the evolution away from a monolithic libgcc2.c seems like
a reasonable "software engineering" compromise.  However, the other major
possibilities are to either just not fix this problem for 4.2, or go for
the more significant reorganization now (probably using macros akin
to GLIBC's soft-fp as you suggest above).

I don't have maintainership over libgcc, so it's not my call.  But
there's currently only one patch/suggestion on the table which limits
the options.  But if you'd like me (or Daniel) to look into other
possibilities, just let me (us) know.

Roger
--