diff options
| author | Patrick Palka <patrick@parcs.ath.cx> | 2015-08-29 18:16:40 -0400 |
|---|---|---|
| committer | Patrick Palka <patrick@parcs.ath.cx> | 2015-09-02 20:50:46 -0400 |
| commit | eed8b28a07c32f835dfb4ff21fb9c0bf33c738df (patch) | |
| tree | fdaccb1794d62811bb49a3e78f14b4211c50fccc /gdb/gdb_obstack.c | |
| parent | 8cbebaac8f387aa0987410243c9f0d3a51041750 (diff) | |
| download | binutils-eed8b28a07c32f835dfb4ff21fb9c0bf33c738df.zip binutils-eed8b28a07c32f835dfb4ff21fb9c0bf33c738df.tar.gz binutils-eed8b28a07c32f835dfb4ff21fb9c0bf33c738df.tar.bz2 | |
Update documentation of function copy_type_recursive
Following commit 8f57eec2fb3 ("Use gdbarch obstack to allocate types in
alloc_type_arch") it is no longer the case that the type returned by
copy_type_recursive is allocated using malloc. Because the function
uses alloc_type_arch internally, the new type is now allocated on the
gdbarch associated with the type, and is thus owned by that gdbarch.
gdb/ChangeLog:
* gdbtypes.c (copy_type_recursive): Update documentation.
Diffstat (limited to 'gdb/gdb_obstack.c')
0 files changed, 0 insertions, 0 deletions