Re: Remove the frame size argument from function_prologue/epilogue

2017-08-23 Thread Richard Sandiford
Mike Stump writes: > On Aug 21, 2017, at 4:12 AM, Richard Sandiford > wrote: >> >> Later patches will add support for frame sizes that are a run-time >> invariant but not a compile-time constant. > > I'm assuming dwarf and C++ exceptions will remain working. :-) Sure :-) The vector length is

Re: Remove the frame size argument from function_prologue/epilogue

2017-08-22 Thread Mike Stump
On Aug 21, 2017, at 4:12 AM, Richard Sandiford wrote: > > Later patches will add support for frame sizes that are a run-time > invariant but not a compile-time constant. I'm assuming dwarf and C++ exceptions will remain working. :-)

Re: Remove the frame size argument from function_prologue/epilogue

2017-08-21 Thread Richard Biener
On Mon, Aug 21, 2017 at 1:12 PM, Richard Sandiford wrote: > Later patches will add support for frame sizes that are a run-time > invariant but not a compile-time constant. This then raised the > question of whether the frame size argument to the function_prologue/ > epilogue hooks should be updat

Remove the frame size argument from function_prologue/epilogue

2017-08-21 Thread Richard Sandiford
Later patches will add support for frame sizes that are a run-time invariant but not a compile-time constant. This then raised the question of whether the frame size argument to the function_prologue/ epilogue hooks should be updated accordingly. It turned out that only two targets actually used