This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
> But GCC people and not libc people are the ones who decide what > the libgcc interface is that gcc -ffree-standing emits code for. It looks like "software floating point" is a special exception. When compiling on a processor without an FPU, such as H8300, or even x86 with "-msoft-float -mno-ret-in-387", GCC emits code that contains calls to a suitable software floating point library. These generic routines are not part of libgcc, and on most platforms aren't part of glibc by default. From my searches of the internet, it looks like the main library that implements these routines appears to be the "soft-fp" directory of glibc. Given that this is the principal implementation of this API, I don't think GCC should emit calls to functions that it doesn't support. I must admit that I was a bit surprised that soft-fp wasn't part of libgcc, nor GCC, nor binutils, nor newlib, nor src. But if glibc is its home, this is where I should send the patches... Roger --
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |