These are just regular local variables that are not accessed in any
funny ways, not even though a pointer. There's absolutely no reason to
declare them volatile. It only ends up hurting the quality of the
generated machine code.
If anything, it would make sense to decalre sigsp as *pointing* to
volatile memory (volatile void *sigsp), but evidently that's not needed
either.
Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
Message-Id: <
20230403115621.258636-2-bugaevc@gmail.com>
_hurd_setup_sighandler (struct hurd_sigstate *ss, const struct sigaction *action,
__sighandler_t handler,
int signo, struct hurd_signal_detail *detail,
- volatile int rpc_wait,
+ int rpc_wait,
struct machine_thread_all_state *state)
{
#error "Need to write sysdeps/mach/hurd/MACHINE/trampoline.c"
_hurd_setup_sighandler (struct hurd_sigstate *ss, const struct sigaction *action,
__sighandler_t handler,
int signo, struct hurd_signal_detail *detail,
- volatile int rpc_wait,
+ int rpc_wait,
struct machine_thread_all_state *state)
{
void trampoline (void);
void rpc_wait_trampoline (void);
void firewall (void);
- void *volatile sigsp;
+ void *sigsp;
struct sigcontext *scp;
struct
{