On Tue, Dec 10, 2013 at 02:54:46AM +0400, Vadim Girlin wrote:
> On Mon, 2013-12-09 at 10:56 -0500, Tom Stellard wrote:
> > On Sat, Dec 07, 2013 at 07:06:36PM +0400, Vadim Girlin wrote:
> > > On evergreen we have to reserve 1 stack element in some additional cases
> > > besides the ones mentioned in
On Mon, 2013-12-09 at 10:56 -0500, Tom Stellard wrote:
> On Sat, Dec 07, 2013 at 07:06:36PM +0400, Vadim Girlin wrote:
> > On evergreen we have to reserve 1 stack element in some additional cases
> > besides the ones mentioned in the docs, but stack size computation was
> > recently reimplemented e
On Sat, Dec 07, 2013 at 07:06:36PM +0400, Vadim Girlin wrote:
> On evergreen we have to reserve 1 stack element in some additional cases
> besides the ones mentioned in the docs, but stack size computation was
> recently reimplemented exactly as described in the docs by the patch that
> added worka
On Sat, Dec 07, 2013 at 07:06:36PM +0400, Vadim Girlin wrote:
> On evergreen we have to reserve 1 stack element in some additional cases
> besides the ones mentioned in the docs, but stack size computation was
> recently reimplemented exactly as described in the docs by the patch that
> added worka
On evergreen we have to reserve 1 stack element in some additional cases
besides the ones mentioned in the docs, but stack size computation was
recently reimplemented exactly as described in the docs by the patch that
added workarounds for stack issues on EG/CM, resulting in regressions
with some a
