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>
47 lines
1.2 KiB
C
47 lines
1.2 KiB
C
#ifndef CRIS_TARGET_SYSCALL_H
|
|
#define CRIS_TARGET_SYSCALL_H
|
|
|
|
#define UNAME_MACHINE "cris"
|
|
#define UNAME_MINIMUM_RELEASE "2.6.32"
|
|
|
|
/* pt_regs not only specifices the format in the user-struct during
|
|
* ptrace but is also the frame format used in the kernel prologue/epilogues
|
|
* themselves
|
|
*/
|
|
|
|
struct target_pt_regs {
|
|
unsigned long orig_r10;
|
|
/* pushed by movem r13, [sp] in SAVE_ALL. */
|
|
unsigned long r0;
|
|
unsigned long r1;
|
|
unsigned long r2;
|
|
unsigned long r3;
|
|
unsigned long r4;
|
|
unsigned long r5;
|
|
unsigned long r6;
|
|
unsigned long r7;
|
|
unsigned long r8;
|
|
unsigned long r9;
|
|
unsigned long r10;
|
|
unsigned long r11;
|
|
unsigned long r12;
|
|
unsigned long r13;
|
|
unsigned long acr;
|
|
unsigned long srs;
|
|
unsigned long mof;
|
|
unsigned long spc;
|
|
unsigned long ccs;
|
|
unsigned long srp;
|
|
unsigned long erp; /* This is actually the debugged process' PC */
|
|
/* For debugging purposes; saved only when needed. */
|
|
unsigned long exs;
|
|
unsigned long eda;
|
|
};
|
|
|
|
#define TARGET_CLONE_BACKWARDS2
|
|
#define TARGET_MINSIGSTKSZ 2048
|
|
#define TARGET_MLOCKALL_MCL_CURRENT 1
|
|
#define TARGET_MLOCKALL_MCL_FUTURE 2
|
|
|
|
#endif
|