3622634bc6
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>
23 lines
509 B
C
23 lines
509 B
C
#ifndef SH4_TARGET_SYSCALL_H
|
|
#define SH4_TARGET_SYSCALL_H
|
|
|
|
struct target_pt_regs {
|
|
unsigned long regs[16];
|
|
unsigned long pc;
|
|
unsigned long pr;
|
|
unsigned long sr;
|
|
unsigned long gbr;
|
|
unsigned long mach;
|
|
unsigned long macl;
|
|
long tra;
|
|
};
|
|
|
|
#define UNAME_MACHINE "sh4"
|
|
#define UNAME_MINIMUM_RELEASE "2.6.32"
|
|
|
|
#define TARGET_MINSIGSTKSZ 2048
|
|
#define TARGET_MLOCKALL_MCL_CURRENT 1
|
|
#define TARGET_MLOCKALL_MCL_FUTURE 2
|
|
|
|
#endif /* SH4_TARGET_SYSCALL_H */
|