diff options
author | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2009-12-07 12:52:05 +0100 |
---|---|---|
committer | Martin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com> | 2009-12-07 12:51:36 +0100 |
commit | 39475179d40996b4efa662e3825735a84d2526d1 (patch) | |
tree | 272e70b862bac408de84541d17adde0cd42d51ac /tools | |
parent | 369a46325d07061e0f66e16a1f59ef4f526a6464 (diff) | |
download | linux-3.10-39475179d40996b4efa662e3825735a84d2526d1.tar.gz linux-3.10-39475179d40996b4efa662e3825735a84d2526d1.tar.bz2 linux-3.10-39475179d40996b4efa662e3825735a84d2526d1.zip |
[S390] Improve code generated by atomic operations.
Git commit ea435467500612636f8f4fb639ff6e76b2496e4b changed the
definition of atomic_t and atomic64_t for s390 by adding the volatile
modifier to the counter field. This has an unfortunate side effect
with newer versions of the gcc. The typeof operator now picks up the
volatile modifier from the expression. This causes the compiler to
think that it has to store the two temporary variable old_val and
new_val in the __CS_LOOP for the different atomic operations to the
stack as the variables are now volatile. Both stores are superfluous.
The hack to replace typeof(ptr->counter) with int in __CS_LOOP and
and long long in __CSG_LOOP avoids the two stores. A better solution
would be to drop the volatile from the counter field of the atomic_t
and atomic64_t definition. But that is a touchy subject ..
Cc: Matthew Wilcox <matthew@wil.cx>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions