From 6bba70b0ec269c53e46c2f36156fc802b3c763a6 Mon Sep 17 00:00:00 2001
From: Michael Sevakis <jethead71@rockbox.org>
Date: Mon, 25 Jun 2007 20:46:54 +0000
Subject: current_tick really does need to be volatile since gcc can optimize
 away checking the value otherwise - found out the hard way. :)

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@13715 a1c6a512-1295-4272-9138-f99709370657
---
 apps/plugin.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'apps')

diff --git a/apps/plugin.h b/apps/plugin.h
index a95d80b7aa..3b9ca03e32 100644
--- a/apps/plugin.h
+++ b/apps/plugin.h
@@ -334,7 +334,7 @@ struct plugin_api {
 #ifdef HAVE_PRIORITY_SCHEDULING
     void (*priority_yield)(void);
 #endif
-    long* current_tick;
+    volatile long* current_tick;
     long (*default_event_handler)(long event);
     long (*default_event_handler_ex)(long event, void (*callback)(void *), void *parameter);
     struct thread_entry* threads;
-- 
cgit v1.2.3