Re: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default

2018-04-10 Thread Segher Boessenkool
Hi! On Thu, Apr 05, 2018 at 01:07:21PM -0400, David Edelsohn wrote: > I don't have a fundamental objection. AIX does use DWARF EH. I'm not > worried about the EH processing itself, but this may trigger paths in > dwarf2out, etc. that aren't prepared for AIX XCOFF. I'm concerned that > it may assu

Re: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default

2018-04-05 Thread David Edelsohn
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

Re: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default

2018-04-05 Thread Jakub Jelinek
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

Re: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default

2018-04-05 Thread Jakub Jelinek
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

Re: [PATCH] rs6000: Enable -fasynchronous-unwind-tables by default

2018-04-05 Thread Segher Boessenkool
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