diff options
author | Peter Zijlstra <[email protected]> | 2015-08-12 21:04:22 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2015-08-13 08:44:43 +0200 |
commit | d420acd816c07c7be31bd19d09cbcb16e5572fa6 (patch) | |
tree | 4d66213e5f6ee3ad6b4ba769bd595f362273dd4d /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 0ca326de7aa9cb253db9c1a3eb3f0487c8dbf912 (diff) |
jump_label/x86: Work around asm build bug on older/backported GCCs
Boris reported that gcc version 4.4.4 20100503 (Red Hat
4.4.4-2) fails to build linux-next kernels that have
this fresh commit via the locking tree:
11276d5306b8 ("locking/static_keys: Add a new static_key interface")
The problem appears to be that even though @key and @branch are
compile time constants, it doesn't see the following expression
as an immediate value:
&((char *)key)[branch]
More recent GCCs don't appear to have this problem.
In particular, Red Hat backported the 'asm goto' feature into 4.4,
'normal' 4.4 compilers will not have this feature and thus not
run into this asm.
The workaround is to supply both values to the asm as immediates
and do the addition in asm.
Suggested-by: H. Peter Anvin <[email protected]>
Reported-by: Boris Ostrovsky <[email protected]>
Tested-by: Boris Ostrovsky <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions