diff options
author | Nick Alcock <nick.alcock@oracle.com> | 2021-05-06 09:30:58 +0100 |
---|---|---|
committer | Nick Alcock <nick.alcock@oracle.com> | 2021-05-06 09:30:59 +0100 |
commit | 49da556c658684db1b8bdba956e541bc99628f02 (patch) | |
tree | a116f7a2004adbeb9f597dfa0397c2a969460853 /libctf/libctf.ver | |
parent | 15091ded14ec08bd3f3a686d420c6009e1d2c518 (diff) | |
download | gdb-49da556c658684db1b8bdba956e541bc99628f02.zip gdb-49da556c658684db1b8bdba956e541bc99628f02.tar.gz gdb-49da556c658684db1b8bdba956e541bc99628f02.tar.bz2 |
libctf, include: support an alternative encoding for nonrepresentable types
Before now, types that could not be encoded in CTF were represented as
references to type ID 0, which does not itself appear in the
dictionary. This choice is annoying in several ways, principally that it
forces generators and consumers of CTF to grow special cases for types
that are referenced in valid dicts but don't appear.
Allow an alternative representation (which will become the only
representation in format v4) whereby nonrepresentable types are encoded
as actual types with kind CTF_K_UNKNOWN (an already-existing kind
theoretically but not in practice used for padding, with value 0).
This is backward-compatible, because CTF_K_UNKNOWN was not used anywhere
before now: it was used in old-format function symtypetabs, but these
were never emitted by any compiler and the code to handle them in libctf
likely never worked and was removed last year, in favour of new-format
symtypetabs that contain only type IDs, not type kinds.
In order to link this type, we need an API addition to let us add types
of unknown kind to the dict: we let them optionally have names so that
GCC can emit many different unknown types and those types with identical
names will be deduplicated together. There are also small tweaks to the
deduplicator to actually dedup such types, to let opening of dicts with
unknown types with names work, to return the ECTF_NONREPRESENTABLE error
on resolution of such types (like ID 0), and to print their names as
something useful but not a valid C identifier, mostly for the sake of
the dumper.
Tests added in the next commit.
include/ChangeLog
2021-05-06 Nick Alcock <nick.alcock@oracle.com>
* ctf.h (CTF_K_UNKNOWN): Document that it can be used for
nonrepresentable types, not just padding.
* ctf-api.h (ctf_add_unknown): New.
libctf/ChangeLog
2021-05-06 Nick Alcock <nick.alcock@oracle.com>
* ctf-open.c (init_types): Unknown types may have names.
* ctf-types.c (ctf_type_resolve): CTF_K_UNKNOWN is as
non-representable as type ID 0.
(ctf_type_aname): Print unknown types.
* ctf-dedup.c (ctf_dedup_hash_type): Do not early-exit for
CTF_K_UNKNOWN types: they have real hash values now.
(ctf_dedup_rwalk_one_output_mapping): Treat CTF_K_UNKNOWN types
like other types with no referents: call the callback and do not
skip them.
(ctf_dedup_emit_type): Emit via...
* ctf-create.c (ctf_add_unknown): ... this new function.
* libctf.ver (LIBCTF_1.2): Add it.
Diffstat (limited to 'libctf/libctf.ver')
-rw-r--r-- | libctf/libctf.ver | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libctf/libctf.ver b/libctf/libctf.ver index 8c362f3..0b182f3 100644 --- a/libctf/libctf.ver +++ b/libctf/libctf.ver @@ -201,4 +201,5 @@ LIBCTF_1.2 { global: ctf_lookup_by_symbol_name; ctf_arc_lookup_symbol_name; + ctf_add_unknown; } LIBCTF_1.1; |