<offlist> or1k printf causes crash

[Hesham Moustafa]

On Thu, Aug 21, 2014 at 11:04 PM, Christian Svensson <christian at cmd.nu> wrote:
> On Thu, Aug 21, 2014 at 9:56 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> The sp must be updated before the memory can be used. This is just
>> a bug otherwise.
>
> No, 128 byte redzone is an ABI thing both that OpenRISC and x86-64 have.
> The bug in GCC was that redzone was not respected IIRC (if it's the
> same bug that I have in mind).
>
>> R1 [SP]
>> The stack pointer holds the limit of the current stack frame. The first 128 bytes below the stack pointer are reserved for leaf functions, and below that are undefined. Stack pointer must be word aligned at all times.
>
>> Christian.. can you review that code?
> Could you point me to the code? I don't know exactly which code and
> version is being used.

ISR_Handler code goes there:

https://github.com/RTEMS/rtems/blob/master/c/src/lib/libbsp/or1k/or1ksim/start/start.S
https://github.com/RTEMS/rtems/blob/master/cpukit/score/cpu/or1k/or1k-exception-handler-low.S

and context switch code:
https://github.com/RTEMS/rtems/blob/master/cpukit/score/cpu/or1k/or1k-context-switch.S