Weird FIXME about mini-arm-os HOT 4 CLOSED

While developing mini-arm-os, I encountered a bug triggered by GCC optimizations (version 5.x).

You can check again for the generated instructions by recent GNU toolchain. Such workaround should be eliminated.

from mini-arm-os.

@lecopzer, any further evidence?

from mini-arm-os.

Sorry for suspending this issue.

PendSV is not only an interrupt handler but where the context switch happends
r7 is usually used to preserve system call number (isr number).

Without __attribute__, it looks like:

80005c8: b480        push  {r7} 
80005ca: af00        add r7, sp, #0
 /* Save the old task's context */
 asm volatile("mrs   r0, psp\n"
80005cc: f3ef 8009   mrs r0, PSP

But our pendsv_handler has context switch code at end of

asm volatile("mov r0, %0\n" : : "r" (tasks[lastTask].stack));
   40       /* Restore the new task's context and jump to the task */
   41       asm volatile("ldmia r0!, {r4-r11, lr}\n"
   42                    "msr psp, r0\n"
   43                    "bx lr\n");

The core register was changed here and we even have our own return code (line 41 to 43)
that the compiler will never know this.

Compiler don't know we handle core register and stack in C function in our own
and will never assume user "corrupt" calling convention.
Compiler is doing its jobs performing regular push r7 and pop r7
Even in 7.2.1 arm-eabi compiler, there is still push r7 in pendsv_handler

So it's reasonable to have naked attribute where we do the context switch or have our own register/stack handling in C function and should not be a FIXME.

from mini-arm-os.

I agree. Please send another pull request to revise the existing C comment to reflect its necessity. It is no longer "FIXME". Instead, it appears with "Caution".

from mini-arm-os.