On Fri, Jun 10, 2011 at 1:45 AM, Mark Heffernan meh...@google.com wrote:
On Wed, Jun 8, 2011 at 1:54 AM, Richard Guenther
richard.guent...@gmail.com wrote:
Well, it's still not a hard limit as we can't tell how many spill slots
or extra call argument or return value slots we need.
Agreed.
On Wed, Jun 8, 2011 at 1:54 AM, Richard Guenther
richard.guent...@gmail.com wrote:
Well, it's still not a hard limit as we can't tell how many spill slots
or extra call argument or return value slots we need.
Agreed. It's not perfect. But I've found this does a reasonable job
of preventing
On Wed, Jun 8, 2011 at 1:36 AM, Xinliang David Li davi...@google.com wrote:
Ok for google/main. A good candidate patch for trunk too.
Well, it's still not a hard limit as we can't tell how many spill slots
or extra call argument or return value slots we need.
Richard.
Thanks,
David
On
Ok for google/main. A good candidate patch for trunk too.
Thanks,
David
On Tue, Jun 7, 2011 at 4:29 PM, Mark Heffernan meh...@google.com wrote:
This patch pessimizes stack accounting during inlining. This enables
setting a firm stack size limit (via parameters large-stack-frame and
