From 7aab81edce830e15134b52256ad3186e08951b10 Mon Sep 17 00:00:00 2001 From: Vincent Palatin Date: Thu, 6 Mar 2014 16:02:58 -0800 Subject: force the compiler to use a valid register allocation for irq handlers When we are calling the re-scheduling routine at the end of an irq handling routine, we need to ensure that the high registers are not currently saved on the system stack. On Cortex-M3/M4, the compiler is normally doing tail-call optimization there and behaving properly, but this fixes the fact that insanely large interrupt handling routines where sometimes not compile and not running properly (aka issue 24515). This also prepares for one more core-specific DECLARE_IRQ routine on Cortex-M0. Note: now on, the IRQ handling routines should no longer be "static". Signed-off-by: Vincent Palatin BRANCH=none BUG=chrome-os-partner:24515 TEST=make -j buildall revert the workaround for 24515, see the issue happening only without this CL. Change-Id: Ic419369231925568df05815fd079ed191a5446db Reviewed-on: https://chromium-review.googlesource.com/189153 Reviewed-by: Vic Yang Reviewed-by: Randall Spangler Commit-Queue: Vincent Palatin Tested-by: Vincent Palatin --- chip/lm4/system.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chip/lm4/system.c') diff --git a/chip/lm4/system.c b/chip/lm4/system.c index 0741d0c7f3..6a55b2941e 100644 --- a/chip/lm4/system.c +++ b/chip/lm4/system.c @@ -316,7 +316,7 @@ void system_reset_rtc_alarm(void) /** * Hibernate module interrupt */ -static void __hibernate_irq(void) +void __hibernate_irq(void) { system_reset_rtc_alarm(); } -- cgit v1.2.1