On 09/19/2016 03:45 AM, Richard Earnshaw (lists) wrote:
So those don't seem to me to imply that the frame pointer needs to be a
fixed register. So the first thing I'd do is fix the aarch64 port to
not do that and see what fallout there is and how to fix it.
Most ports simply don't mark the fra
On 15/09/16 17:36, Jeff Law wrote:
> On 09/13/2016 05:10 AM, Tamar Christina wrote:
>> Hi Jeff,
>>
>>
>> On 12/09/16 18:16, Jeff Law wrote:
>>> On 09/05/2016 08:59 AM, Tamar Christina wrote:
Hi All,
This patch allows the FP register to be used as a call-saved
register when -fomi
On 09/13/2016 05:10 AM, Tamar Christina wrote:
Hi Jeff,
On 12/09/16 18:16, Jeff Law wrote:
On 09/05/2016 08:59 AM, Tamar Christina wrote:
Hi All,
This patch allows the FP register to be used as a call-saved
register when -fomit-frame-pointer is used.
The change is done in such a way that th
Hi Jeff,
On 12/09/16 18:16, Jeff Law wrote:
On 09/05/2016 08:59 AM, Tamar Christina wrote:
Hi All,
This patch allows the FP register to be used as a call-saved
register when -fomit-frame-pointer is used.
The change is done in such a way that the defaults do not change.
To use the FP register
On 09/05/2016 08:59 AM, Tamar Christina wrote:
Hi All,
This patch allows the FP register to be used as a call-saved
register when -fomit-frame-pointer is used.
The change is done in such a way that the defaults do not change.
To use the FP register both -fomit-frame-pointer and
-fcall-saved- ne
On Mon, Sep 05, 2016 at 03:59:18PM +0100, Tamar Christina wrote:
> Hi All,
>
> This patch allows the FP register to be used as a call-saved
> register when -fomit-frame-pointer is used.
>
> The change is done in such a way that the defaults do not change.
> To use the FP register both -fomit-fram
