forked from Imagelibrary/binutils-gdb
libctf: fix comment above ctf_dict_t
It is perfectly possible to have dynamically allocated data owned by a specific dict: you just have to teach ctf_serialize about it. libctf/ChangeLog 2021-03-18 Nick Alcock <nick.alcock@oracle.com> * ctf-impl.h (ctf_dict_t): Fix comment.
This commit is contained in:
@@ -1,3 +1,7 @@
|
|||||||
|
2021-03-18 Nick Alcock <nick.alcock@oracle.com>
|
||||||
|
|
||||||
|
* ctf-impl.h (ctf_dict_t): Fix comment.
|
||||||
|
|
||||||
2021-03-18 Nick Alcock <nick.alcock@oracle.com>
|
2021-03-18 Nick Alcock <nick.alcock@oracle.com>
|
||||||
|
|
||||||
* ctf-create.c (symtypetab_delete_nonstatic_vars): Move
|
* ctf-create.c (symtypetab_delete_nonstatic_vars): Move
|
||||||
|
|||||||
@@ -372,11 +372,12 @@ typedef struct ctf_dedup
|
|||||||
ctf_dict_t typedef appears in <ctf-api.h> and declares a forward tag.
|
ctf_dict_t typedef appears in <ctf-api.h> and declares a forward tag.
|
||||||
(A ctf_file_t typedef also appears there, for historical reasons.)
|
(A ctf_file_t typedef also appears there, for historical reasons.)
|
||||||
|
|
||||||
NOTE: ctf_serialize() requires that everything inside of ctf_dict either be
|
NOTE: ctf_serialize requires that everything inside of ctf_dict either be an
|
||||||
an immediate value, a pointer to dynamically allocated data *outside* of the
|
immediate value, a pointer to dynamically allocated data *outside* of the
|
||||||
ctf_dict itself, or a pointer to statically allocated data. If you add a
|
ctf_dict itself, a pointer to statically allocated data, or specially handled
|
||||||
pointer to ctf_dict that points to something within the ctf_dict itself, you
|
in ctf_serialize. If you add a pointer to ctf_dict that points to something
|
||||||
must make corresponding changes to ctf_serialize(). */
|
within the ctf_dict itself, you must make corresponding changes to
|
||||||
|
ctf_serialize. */
|
||||||
|
|
||||||
struct ctf_dict
|
struct ctf_dict
|
||||||
{
|
{
|
||||||
|
|||||||
Reference in New Issue
Block a user