until we have
time to sort it out.
Tested on powerpc64-linux and on powerpc-ibm-aix7.2.0.0 .
Segher
---
From: Segher Boessenkool
Date: Thu, 5 Apr 2018 09:27:31 +
Subject: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default
To find out where on-entry register values live at any
On Thu, Apr 5, 2018 at 5:50 AM, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
>> To find out where on-entry register values live at any point in a
>> program, GDB currently tries to parse to parse the executable code.
>> This does not work very well, fo
On Thu, Apr 05, 2018 at 05:08:36AM -0500, Segher Boessenkool wrote:
> On Thu, Apr 05, 2018 at 11:50:38AM +0200, Jakub Jelinek wrote:
> > On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> > > To find out where on-entry register values live at any point in a
> > > program, GDB cur
On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> To find out where on-entry register values live at any point in a
> program, GDB currently tries to parse to parse the executable code.
> This does not work very well, for example it gets confused if some
> accesses to the stack
On Thu, Apr 05, 2018 at 11:50:38AM +0200, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> > To find out where on-entry register values live at any point in a
> > program, GDB currently tries to parse to parse the executable code.
> > This does not work v
To find out where on-entry register values live at any point in a
program, GDB currently tries to parse to parse the executable code.
This does not work very well, for example it gets confused if some
accesses to the stack use the frame pointer (r31) and some use the
stack pointer (r1). A symptom
