commit | 0b84653fd94d89c06b677954331c1f8bfe7ad817 | [log] [tgz] |
---|---|---|
author | Giuliano Procida <gprocida@google.com> | Thu Jul 07 08:44:55 2022 +0100 |
committer | Giuliano Procida <gprocida@google.com> | Tue Jul 19 10:16:29 2022 +0100 |
tree | adab57fdbfc8aaec67057713deb8f3aed7f405ff | |
parent | 90c80de49ea077ad549bad9244a4accaf58ef880 [diff] |
Abigail reader: split into type, corpus and document handling libabigail XML can represent the ABI for a single binary object (a.k.a. corpus) or for a group of objects (such as vmlinux plus modules; a.k.a. corpus group). Type information can be spread across the whole document, but symbol and alias information is scoped by corpus. This change ensures that symbol/alias processing is performed per corpus and factors out common type information handling into its own class. PiperOrigin-RevId: 459445566 Change-Id: I1f1967cd35b23f9d5b6fc36dc9e72118fe80c4a9
The STG (symbol-type graph) is an ABI representation and this project contains tools for the creation and comparison of such representations. At present parsers exist for libabigail's ABI XML (C types only) and BTF. The ABI diff tool, stgdiff, supports multiple reporting options. This software currently depends on libabigail for ELF symbol functionality, on libxml2 for XML parsing and on Linux UAPI headers for BTF types.
TBD
See CONTRIBUTING.md for details.