43e0c3515d
Reuse of the same guard symbol in multiple headers is okay as long as
they cannot be included together. scripts/clean-header-guards.pl
can't tell, so it warns.
Since we can avoid guard symbol reuse easily, do so: use guard symbol
${target^^}_${fname^^} for linux-user/$target/$fname, just like we did
in commit a9c94277f0..3500385697.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20190315145123.28030-4-armbru@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
22 lines
477 B
C
22 lines
477 B
C
#ifndef NIOS2_TARGET_SIGNAL_H
|
|
#define NIOS2_TARGET_SIGNAL_H
|
|
|
|
/* this struct defines a stack used during syscall handling */
|
|
|
|
typedef struct target_sigaltstack {
|
|
abi_long ss_sp;
|
|
abi_ulong ss_size;
|
|
abi_long ss_flags;
|
|
} target_stack_t;
|
|
|
|
/* sigaltstack controls */
|
|
#define TARGET_SS_ONSTACK 1
|
|
#define TARGET_SS_DISABLE 2
|
|
|
|
#define TARGET_MINSIGSTKSZ 2048
|
|
#define TARGET_SIGSTKSZ 8192
|
|
|
|
#include "../generic/signal.h"
|
|
|
|
#endif /* NIOS2_TARGET_SIGNAL_H */
|