ARM: 8300/1: teach __asmeq that r11 == fp and r12 == ip
The __asmeq macro is used inside inline asm statements to ensure that register asm variables that explicitly specify a register are mapped correctly onto those registers when used in inline asm input and output constraints. However, the string based matching fails to take into account that 'fp' is often referred to as 'r11' and 'ip' is often referred to as 'r12', (e.g., by clang), causing false negatives. Fix this by making __asmeq consider the ("fp","r11"), ("r11","fp"), ("ip","r12") and ("r12","ip") cases specifically. Reviewed-by: Alex Elder <elder@linaro.org> Acked-by: Nicolas Pitre <nico@linaro.org> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
This commit is contained in:
parent
7a06192834
commit
ada63d4074
1 changed files with 14 additions and 1 deletions
|
@ -8,8 +8,21 @@
|
|||
* This string is meant to be concatenated with the inline asm string and
|
||||
* will cause compilation to stop on mismatch.
|
||||
* (for details, see gcc PR 15089)
|
||||
* For compatibility with clang, we have to specifically take the equivalence
|
||||
* of 'r11' <-> 'fp' and 'r12' <-> 'ip' into account as well.
|
||||
*/
|
||||
#define __asmeq(x, y) ".ifnc " x "," y " ; .err ; .endif\n\t"
|
||||
#define __asmeq(x, y) \
|
||||
".ifnc " x "," y "; " \
|
||||
".ifnc " x y ",fpr11; " \
|
||||
".ifnc " x y ",r11fp; " \
|
||||
".ifnc " x y ",ipr12; " \
|
||||
".ifnc " x y ",r12ip; " \
|
||||
".err; " \
|
||||
".endif; " \
|
||||
".endif; " \
|
||||
".endif; " \
|
||||
".endif; " \
|
||||
".endif\n\t"
|
||||
|
||||
|
||||
#endif /* __ASM_ARM_COMPILER_H */
|
||||
|
|
Loading…
Reference in a new issue