From 645da826bba8c37d834403a56dc94203052c2cee Mon Sep 17 00:00:00 2001 From: Sergey Bugaev Date: Mon, 3 Apr 2023 14:56:20 +0300 Subject: hurd: Do not declare local variables volatile 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 Message-Id: <20230403115621.258636-2-bugaevc@gmail.com> --- hurd/trampoline.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'hurd') diff --git a/hurd/trampoline.c b/hurd/trampoline.c index 5bd8dec919..1447b13fe6 100644 --- a/hurd/trampoline.c +++ b/hurd/trampoline.c @@ -29,7 +29,7 @@ struct sigcontext * _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" -- cgit 1.4.1