From dfcab42a0192b2bd0bb43eb609acf19a5613ec9e Mon Sep 17 00:00:00 2001 From: Alexey Lapshin Date: Fri, 5 May 2023 13:35:19 +0800 Subject: [PATCH] pthread: fix restrict keyword usage in function declarations See https://gcc.gnu.org/onlinedocs/gcc/Restricted-Pointers.html --- components/pthread/include/semaphore.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/components/pthread/include/semaphore.h b/components/pthread/include/semaphore.h index 5a7ef56b97..31d47d2072 100644 --- a/components/pthread/include/semaphore.h +++ b/components/pthread/include/semaphore.h @@ -51,7 +51,7 @@ int sem_post(sem_t *sem); * * It is possible, though unlikely, that the task is preempted directly after the timeout calculation, * delaying timeout of the following blocking operating system call by the duration of the preemption. */ -int sem_timedwait(sem_t * restrict semaphore, const struct timespec *restrict abstime); +int sem_timedwait(sem_t *semaphore, const struct timespec *abstime); /** * This is a POSIX function, please refer to the POSIX specification for a detailed description. @@ -66,7 +66,7 @@ int sem_wait(sem_t *sem); /** * This is a POSIX function, please refer to the POSIX specification for a detailed description. */ -int sem_getvalue(sem_t *restrict sem, int *restrict sval); +int sem_getvalue(sem_t *sem, int *sval); #ifdef __cplusplus }