diff options
| author | Mark Wielaard <mark@klomp.org> | 2017-03-13 18:26:47 +0000 |
|---|---|---|
| committer | Mark Wielaard <mark@gcc.gnu.org> | 2017-03-13 18:26:47 +0000 |
| commit | 9905ca975c593e92c0183fdc791f9919edbeb1c8 (patch) | |
| tree | 13f4dfa2660d2841e047b8bd9e6ae7a8ae25c5d8 /gcc | |
| parent | fd231ad75a03bea9e7ac61c57f806740abddcab2 (diff) | |
| download | gcc-9905ca975c593e92c0183fdc791f9919edbeb1c8.zip gcc-9905ca975c593e92c0183fdc791f9919edbeb1c8.tar.gz gcc-9905ca975c593e92c0183fdc791f9919edbeb1c8.tar.bz2 | |
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.
From-SVN: r246105
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions