gcc 4.1 implements compiler builtins for atomic ops
Ulrich Drepper
drepper@redhat.com
Sun Jun 26 23:42:00 GMT 2005
Benjamin Herrenschmidt wrote:
> Yes, but that encourage developers to use them direcltly, which means
> that they'll, for example, produce code that will either be broken for
> 405 or will have a spurrious sync on non-405 which is a significant
> performance issue.
So what? This is an issue for binaries. How many binaries are shared
between reasonable implementations and the broken ones? Don't generate
the sync op by default and tell the losers who use the broken processors
to throw them out or build their own binaries. You can even invent a
mechanism to check for binaries compiled this way.
And go, beat up the processor people. They cause the problems. We
cannot have everybody else suffer from that. We have the APIs for all
kinds of processors and every arch which needs to be treated special
will fall aside since the extra handling is not acceptable to most
programmers.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20050626/57798398/attachment.sig>
More information about the Libc-alpha
mailing list