Re: [PATCH 1/3] Introduce can_implement_as_sibling_call_p

2016-05-20 Thread Kyrill Tkachov
Hi David, On 17/05/16 23:01, David Malcolm wrote: This patch moves part of the logic for determining if tail call optimizations are possible to a new helper function. There are no functional changes. expand_call is 1300 lines long, so there's arguably a case for doing this on its own, but this

Re: [PATCH 1/3] Introduce can_implement_as_sibling_call_p

2016-05-19 Thread Jeff Law
On 05/17/2016 04:01 PM, David Malcolm wrote: This patch moves part of the logic for determining if tail call optimizations are possible to a new helper function. There are no functional changes. expand_call is 1300 lines long, so there's arguably a case for doing this on its own, but this chang

[PATCH 1/3] Introduce can_implement_as_sibling_call_p

2016-05-17 Thread David Malcolm
This patch moves part of the logic for determining if tail call optimizations are possible to a new helper function. There are no functional changes. expand_call is 1300 lines long, so there's arguably a case for doing this on its own, but this change also enables the followup patch. The patch c