On Thu, Sep 29, 2011 at 06:08:50PM +0800, Jiangning Liu wrote:
> As far as I know different back-ends are implementing different
> prologue/epilogue in GCC. If one day this part can be refined and abstracted
> as well, I would say solving this stack-red-zone problem in shared
> prologue/epilogue code would be a perfect solution, and barrier can be
> inserted there.
>
> I'm not saying you are wrong on keeping scheduler using a pure barrier
> interface. From engineering point of view, I only feel my proposal is so far
> so good, because this patch at least solve the problem for all targets in a
> quite simple way. Maybe it can be improved in future based on this.
But you don't want to listen about any other alternative, other backends are
happy with being able to put the best kind of barrier at the best spot
in the epilogue and don't need a "generic" solution which won't model very
well the target diversity anyway.
Jakub
