[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240418031046.4383-2-nihal@nihaljere.xyz>
Date: Wed, 17 Apr 2024 22:10:17 -0500
From: Nihal Jere <nihal@...aljere.xyz>
To: musl@...ts.openwall.com
Cc: Nihal Jere <nihal@...aljere.xyz>
Subject: [PATCH] change __volatile to __volatile__ for consistency
---
These look like the only two occurences of "__volatile" in musl,
elsewhere "__volatile__" is used.
arch/x32/atomic_arch.h | 2 +-
arch/x86_64/atomic_arch.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x32/atomic_arch.h b/arch/x32/atomic_arch.h
index 918c2d4e..eef253db 100644
--- a/arch/x32/atomic_arch.h
+++ b/arch/x32/atomic_arch.h
@@ -44,7 +44,7 @@ static inline void a_or(volatile int *p, int v)
#define a_and_64 a_and_64
static inline void a_and_64(volatile uint64_t *p, uint64_t v)
{
- __asm__ __volatile(
+ __asm__ __volatile__(
"lock ; and %1, %0"
: "=m"(*p) : "r"(v) : "memory" );
}
diff --git a/arch/x86_64/atomic_arch.h b/arch/x86_64/atomic_arch.h
index da4e2037..8753b700 100644
--- a/arch/x86_64/atomic_arch.h
+++ b/arch/x86_64/atomic_arch.h
@@ -53,7 +53,7 @@ static inline void a_or(volatile int *p, int v)
#define a_and_64 a_and_64
static inline void a_and_64(volatile uint64_t *p, uint64_t v)
{
- __asm__ __volatile(
+ __asm__ __volatile__(
"lock ; and %1, %0"
: "=m"(*p) : "r"(v) : "memory" );
}
--
2.43.0
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
