Vasily Gorbik c4e5c229b6 s390/jump_label: use "i" constraint for clang ... Currently kernel build fails under clang if jump labels are enabled. The problem is "X" constraint usage "Any operand whatsoever is allowed", for which clang produces the following: .pushsection __jump_table,"aw" .balign 8 .long 0b-.,.Ltmp577-. .quad %r0+0-. # %r0 is not allowed here .popsection Under gcc constraints "X" or "jdd" (gcc > 9) are used for static keys. Ideally, we'd have used "i" for gcc, but it doesn't work in all cases with -fPIC code. This is gcc-specific problem that doesn't exist in llvm. Since clang does not have "jdd" simply always use "i" constraint for it. Suggested-by: Ulrich Weigand <ulrich.weigand@de.ibm.com> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>		2020-01-22 13:05:35 +01:00
..
asm	s390/jump_label: use "i" constraint for clang	2020-01-22 13:05:35 +01:00
uapi/asm	arch: ipcbuf.h: make uapi asm/ipcbuf.h self-contained	2019-12-04 19:44:14 -08:00