diff options
| author | mark <mark@138bc75d-0d04-0410-961f-82ee72b054a4> | 2017-03-13 18:26:47 +0000 |
|---|---|---|
| committer | mark <mark@138bc75d-0d04-0410-961f-82ee72b054a4> | 2017-03-13 18:26:47 +0000 |
| commit | cb987b84fd492260ef448988dec9f3fe377c4e23 (patch) | |
| tree | 13f4dfa2660d2841e047b8bd9e6ae7a8ae25c5d8 /libiberty/ChangeLog | |
| parent | 5f3975ecdb8569e54869b98d778557b2e085a1a5 (diff) | |
| download | gcc-cb987b84fd492260ef448988dec9f3fe377c4e23.tar.gz | |
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
Diffstat (limited to 'libiberty/ChangeLog')
| -rw-r--r-- | libiberty/ChangeLog | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog index e93e327749d..b513fcefe3e 100644 --- a/libiberty/ChangeLog +++ b/libiberty/ChangeLog @@ -1,3 +1,11 @@ +2017-03-12 Mark Wielaard <mark@klomp.org> + + * 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. + 2017-03-08 Mark Wielaard <mark@klomp.org> PR demangler/70909 |