-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 5 Mar 2005 11:58:29 +0100
Source: python-fam
Binary: python2.3-fam python2.4-fam python-fam
Architecture: source all i386
Version: 1.1-1
Distribution: unstable
Urgency: low
Maintainer: Martin v. Loewis [EMAIL PROTECTED]
Arnd Bergmann [EMAIL PROTECTED] writes:
It would surely be nice to see performance numbers from actual
applications. After all, the applications are normally doing
some things besides low level atomic operations.
Indeed, it would be interesting to find out how often applications
invoke these
Arnd Bergmann [EMAIL PROTECTED] writes:
No, look at my patch again. If you build without i486 optimization,
the compiler will see only the extern declaration for
__exchange_and_add().
I see. What sonames do you suggest to give to the two copies of
libstdc++? You once said you'd call them
Arnd Bergmann [EMAIL PROTECTED] writes:
a) The patch gets merged upstream. It won't hurt anyone who is
building i486+ optimized binaries and fixes a real bug.
Upstream won't accept the patch, because of the performance penalty.
Even if upstream accepts the patch, that won't be before gcc
Arnd Bergmann [EMAIL PROTECTED] writes:
Right. Any reason why the patch below should not work?
Yes, plenty.
When __exchange_and_add is an extern function, the implementation
does not matter to applications using it. Binaries optimized for
i486 or higher can still use the inline function
Arnd Bergmann [EMAIL PROTECTED] writes:
They have to be compiled for i386, as they have always been.
If they were compiled for i486, they would not run on i386
anyway, with or without the bug.
But if they are compiled for i386, they won't run on other Linux
systems, thus losing binary
6 matches
Mail list logo
