Re: [SH] Add simple_return pattern

2012-09-13 Thread Kaz Kojima
Christian Bruel wrote: > The failure turned out to be issues with the profile count and handling > or region partitioning. So, I prefer to handle those separately, > For now, I disable shrink-wrap when partitioning, even if the problem > seems to have disappeared with the more constrained heuristi

Re: [SH] Add simple_return pattern

2012-09-13 Thread Christian Bruel
Hi Kaz, The failure turned out to be issues with the profile count and handling or region partitioning. So, I prefer to handle those separately, For now, I disable shrink-wrap when partitioning, even if the problem seems to have disappeared with the more constrained heuristics. This is probably la

Re: [SH] Add simple_return pattern

2012-09-11 Thread Christian Bruel
On 09/11/2012 03:05 AM, Kaz Kojima wrote: > Christian Bruel wrote: >> This patch implements the simple_return pattern to enable -fshrink-wrap >> on SH. It also clean up some redundancies for expand_epilogue (called >> twice from the "return" and "epilogue" patterns and the >> sh_expand_prologue p

Re: [SH] Add simple_return pattern

2012-09-10 Thread Christian Bruel
On 09/11/2012 12:28 AM, Oleg Endo wrote: > On Mon, 2012-09-10 at 15:51 +0200, Christian Bruel wrote: >> This patch implements the simple_return pattern to enable -fshrink-wrap >> on SH. It also clean up some redundancies for expand_epilogue (called >> twice from the "return" and "epilogue" patter

Re: [SH] Add simple_return pattern

2012-09-10 Thread Kaz Kojima
Christian Bruel wrote: > This patch implements the simple_return pattern to enable -fshrink-wrap > on SH. It also clean up some redundancies for expand_epilogue (called > twice from the "return" and "epilogue" patterns and the > sh_expand_prologue parameter type. > > No regressions with sh-superh

Re: [SH] Add simple_return pattern

2012-09-10 Thread Oleg Endo
On Mon, 2012-09-10 at 15:51 +0200, Christian Bruel wrote: > This patch implements the simple_return pattern to enable -fshrink-wrap > on SH. It also clean up some redundancies for expand_epilogue (called > twice from the "return" and "epilogue" patterns and the > sh_expand_prologue parameter type.