Gabriel Dos Reis writes: > On Wed, 17 Jan 2007, Andrew Haley wrote: > > | > | From a performance/convenience angle, the best place to handle this is > | either libc or the kernel. > > Hmm, that is predicated on assumptions not convenient to users > on targets that are not glibc-based or GNU/Linux-based.
Well, if GNU libc/Linux/whatever can fix this bug in libc or the kernel, so can anyone else. "To a man with a hammer, all things look like a nail." It's very tempting for us in gcc-land always to fix things in gcc, not because it's technically the right place but because it's what we control ourselves. Andrew.
