> Given the description the code looks fine. It would be nice to see
> more of a _why_ in the commit message. I'm guessing this is either
> something related to signal handling, or debugging... I don't see why
> this would be needed for functional correctness.
Committed with additional comment
> Given the description the code looks fine. It would be nice to see
> more of a _why_ in the commit message. I'm guessing this is either
> something related to signal handling, or debugging... I don't see why
> this would be needed for functional correctness.
>
The issue is how we generate a f
* Claudiu Zissulescu [2017-05-19 12:31:01
+0200]:
> From: Claudiu Zissulescu
>
> If the stack pointer is needed, emit a special barrier that will prevent
> the scheduler from moving stores to the frame before the stack adjustment.
>
> 2017-01-03 Claudiu Zissulescu
>
> * config/arc/a
From: Claudiu Zissulescu
If the stack pointer is needed, emit a special barrier that will prevent
the scheduler from moving stores to the frame before the stack adjustment.
2017-01-03 Claudiu Zissulescu
* config/arc/arc.c (arc_expand_prologue): Emit a special barrier
to preve