Some of them use guard symbol TARGET_SYSCALL_H, but we also have CRIS_SYSCALL_H, MICROBLAZE_SYSCALLS_H, TILEGX_SYSCALLS_H and __UC32_SYSCALL_H__. They all upset scripts/clean-header-guards.pl. Reuse of the same guard symbol TARGET_SYSCALL_H in multiple headers is okay as long as they cannot be included together. The script can't tell, so it warns. The script dislikes the other guard symbols, too. They don't match their file name (they should, to make guard collisions less likely), and __UC32_SYSCALL_H__ is a reserved identifier. Clean them all up: use guard symbol $target_TARGET_SYSCALL_H for linux-user/$target/target_sycall.h. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Richard Henderson <rth@twiddle.net>
27 lines
713 B
C
27 lines
713 B
C
#ifndef SPARC64_TARGET_SYSCALL_H
|
|
#define SPARC64_TARGET_SYSCALL_H
|
|
|
|
struct target_pt_regs {
|
|
abi_ulong u_regs[16];
|
|
abi_ulong tstate;
|
|
abi_ulong pc;
|
|
abi_ulong npc;
|
|
abi_ulong y;
|
|
abi_ulong fprs;
|
|
};
|
|
|
|
#define UNAME_MACHINE "sun4u"
|
|
#define UNAME_MINIMUM_RELEASE "2.6.32"
|
|
|
|
/* SPARC kernels don't define this in their Kconfig, but they have the
|
|
* same ABI as if they did, implemented by sparc-specific code which fishes
|
|
* directly in the u_regs() struct for half the parameters in sparc_do_fork()
|
|
* and copy_thread().
|
|
*/
|
|
#define TARGET_CLONE_BACKWARDS
|
|
#define TARGET_MINSIGSTKSZ 4096
|
|
#define TARGET_MLOCKALL_MCL_CURRENT 0x2000
|
|
#define TARGET_MLOCKALL_MCL_FUTURE 0x4000
|
|
|
|
#endif /* SPARC64_TARGET_SYSCALL_H */
|