The comments in cpukit/score/cpu/lm32/rtems/score/cpu.h state that
CPU_STACK_ALIGNMENT should either be 0 or >= CPU_ALIGNMENT. The
latter is 8, the former was 4.

I'm not sure if this fix has any real-life impact on M1 behaviour,
but I guess it can't hurt.

- Werner

Index: cpukit/score/cpu/lm32/rtems/score/cpu.h
===================================================================
RCS file: /usr1/CVS/rtems/cpukit/score/cpu/lm32/rtems/score/cpu.h,v
retrieving revision 1.14
diff -u -r1.14 cpu.h
--- cpukit/score/cpu/lm32/rtems/score/cpu.h     27 Sep 2011 09:17:02 -0000      
1.14
+++ cpukit/score/cpu/lm32/rtems/score/cpu.h     8 Nov 2011 18:27:45 -0000
@@ -695,7 +695,7 @@
  *
  *  XXX document implementation including references if appropriate
  */
-#define CPU_STACK_ALIGNMENT        4
+#define CPU_STACK_ALIGNMENT        0
 
 /*
  *  ISR handler macros
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode

Reply via email to