[pushed/ob] cplus_demangle_fill_component: Handle DEMANGLE_COMPONENT_RVALUE_REFERENCE (Re: [PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.)

2017-03-27 Thread Pedro Alves
[added back gcc-patches, obvious libiberty patch below] On 03/14/2017 10:50 AM, Pedro Alves wrote: > On 03/14/2017 09:04 AM, Mark Wielaard wrote: > >> That looks good. But note that there is one behavioral change. >> cplus_demangle_fill_component is defined as: >> >> /* Fill in most component

Re: [PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.

2017-03-13 Thread Pedro Alves
On 03/13/2017 06:29 PM, Mark Wielaard wrote: > O, sorry. I should have let Nick known about the gdb regressions I found. > Besides this patch gdb needs the following one-liner fix: > > diff --git a/gdb/cp-name-parser.y b/gdb/cp-name-parser.y > index fd1e949..5278c05 100644 > ---

Re: [PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.

2017-03-13 Thread Mark Wielaard
On Mon, Mar 13, 2017 at 07:11:50PM +0100, Markus Trippelsdorf wrote: > On 2017.03.12 at 23:05 +0100, Mark Wielaard wrote: > > While integrating the d_printing recursion guard change into gdb I > > noticed we forgot to initialize the demangle_component d_printing > > field in

Re: [PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.

2017-03-13 Thread Markus Trippelsdorf
On 2017.03.12 at 23:05 +0100, Mark Wielaard wrote: > While integrating the d_printing recursion guard change into gdb I > noticed we forgot to initialize the demangle_component d_printing > field in cplus_demangle_fill_{name,extended_operator,ctor,dtor}. > As is done in

Re: [PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.

2017-03-13 Thread Ian Lance Taylor via gcc-patches
On Sun, Mar 12, 2017 at 3:05 PM, Mark Wielaard wrote: > While integrating the d_printing recursion guard change into gdb I > noticed we forgot to initialize the demangle_component d_printing > field in cplus_demangle_fill_{name,extended_operator,ctor,dtor}. > As is done in

[PATCH] libiberty: Initialize d_printing in all cplus_demangle_* functions.

2017-03-12 Thread Mark Wielaard
While integrating the d_printing recursion guard change into gdb I noticed we forgot to initialize the demangle_component d_printing field in cplus_demangle_fill_{name,extended_operator,ctor,dtor}. As is done in cplus_demangle_fill_{component,builtin_type,operator}. It happened to work because in