]> git.ipfire.org Git - thirdparty/gcc.git/commit
libiberty: Initialize d_printing in all cplus_demangle_fill_* functions.
authormark <mark@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 13 Mar 2017 18:26:47 +0000 (18:26 +0000)
committermark <mark@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 13 Mar 2017 18:26:47 +0000 (18:26 +0000)
commitcb987b84fd492260ef448988dec9f3fe377c4e23
tree13f4dfa2660d2841e047b8bd9e6ae7a8ae25c5d8
parent5f3975ecdb8569e54869b98d778557b2e085a1a5
libiberty: Initialize d_printing in all cplus_demangle_fill_* functions.

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 gcc all demangle_components were
allocated through d_make_empty. But gdb has its own allocation
mechanism (as might other users).

libiberty/ChangeLog:

       * cp-demangle.c (cplus_demangle_fill_name): Initialize
       demangle_component d_printing.
       (cplus_demangle_fill_extended_operator): Likewise.
       (cplus_demangle_fill_ctor): Likewise.
       (cplus_demangle_fill_dtor): Likewise.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@246105 138bc75d-0d04-0410-961f-82ee72b054a4
libiberty/ChangeLog
libiberty/cp-demangle.c