Roger Sayle <[EMAIL PROTECTED]> writes: > Indeed, no good deed ever goes unpunished. In fact, isn't it the MIPS > backend's use of the GOFAST libraries which is one of the major blockers > of adding -msoft-float tests to the testsuite? :-)
No. As I've explained earlier this week, -msoft-float code is simply not link-compatible with -mhard-float code. Mark Mitchell <[EMAIL PROTECTED]> writes: > Andrew Pinski wrote: >>> Andrew Pinski wrote: >>> >>>> Also why revert a patch which obvious works in the default configurations? >>> It eliminates a Fortran problem, but causes a C problem. >> >> I thought it only caused the problem with C code when supplying -msoft-float >> which is not a default configuration? > > C code, compiled with -msoft-float, is very common on MIPS, whether or > not it's a "default configuration". Right. What do people mean by "default configuration"? The primary interest in MIPS these days is as an embedded platform, and the main bare-metal targets (mips-elf, mips64-elf mipsisa32-elf, mipsisa64-elf) all have -msoft-float multilibs. You don't have to do anything special to get them. Richard
