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>
30 lines
683 B
C
30 lines
683 B
C
#ifndef M68K_TARGET_SYSCALL_H
|
|
#define M68K_TARGET_SYSCALL_H
|
|
|
|
/* this struct defines the way the registers are stored on the
|
|
stack during a system call. */
|
|
|
|
struct target_pt_regs {
|
|
abi_long d1, d2, d3, d4, d5, d6, d7;
|
|
abi_long a0, a1, a2, a3, a4, a5, a6;
|
|
abi_ulong d0;
|
|
abi_ulong usp;
|
|
abi_ulong orig_d0;
|
|
int16_t stkadj;
|
|
uint16_t sr;
|
|
abi_ulong pc;
|
|
uint16_t fntvex;
|
|
uint16_t __fill;
|
|
};
|
|
|
|
#define UNAME_MACHINE "m68k"
|
|
#define UNAME_MINIMUM_RELEASE "2.6.32"
|
|
|
|
#define TARGET_MINSIGSTKSZ 2048
|
|
#define TARGET_MLOCKALL_MCL_CURRENT 1
|
|
#define TARGET_MLOCKALL_MCL_FUTURE 2
|
|
|
|
void do_m68k_simcall(CPUM68KState *, int);
|
|
|
|
#endif /* M68K_TARGET_SYSCALL_H */
|