aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2009-09-16 18:58:39 -0700
committerH. Peter Anvin <hpa@zytor.com>2009-09-16 18:58:39 -0700
commitd79514ba4884906a0261bccb0f6e6f4cdae9db3e (patch)
tree87f54167358274947c754469ed9638b0cfc202e9
parent990cb1bd14b4962df2487d3d9f891479e5b11f83 (diff)
downloadlwip-d79514ba4884906a0261bccb0f6e6f4cdae9db3e.tar.gz
lwip-d79514ba4884906a0261bccb0f6e6f4cdae9db3e.tar.xz
lwip-d79514ba4884906a0261bccb0f6e6f4cdae9db3e.zip
jiffies.h: drop "const" from __jiffies
Apparently gcc thinks that "const volatile" means it can move references around -- it doesn't, it just means that it's not permitted to write to a location which is otherwise volatile. Mark it just plain volatile to un-confuse gcc. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
-rw-r--r--com32/include/core/jiffies.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/com32/include/core/jiffies.h b/com32/include/core/jiffies.h
index a8e18060..49087c32 100644
--- a/com32/include/core/jiffies.h
+++ b/com32/include/core/jiffies.h
@@ -10,7 +10,8 @@
typedef uint32_t jiffies_t;
typedef int32_t sjiffies_t;
-extern const volatile jiffies_t __jiffies;
+extern volatile jiffies_t __jiffies;
+
static inline jiffies_t jiffies(void)
{
return __jiffies;