Google Git
Sign in
android / platform / external / stg / refs/heads/android14-qpr2-s1-release
commit16878c9d3b170afb0050375442a4e07bf7ce44f9[log] [tgz]
authorAndroid Build Coastguard Worker <[email protected]>Thu Dec 14 00:16:43 2023 +0000
committerAndroid Build Coastguard Worker <[email protected]>Thu Dec 14 00:16:43 2023 +0000
tree28f4a7080374fadd9599080be9c3d1d31bf01211
parent0c75de504d41ab673214f3b676483bb3a2db0171 [diff]
parent4ffc20011f1b68af77efec5a6f3b352248f7bc25 [diff]
Snap for 11216811 from 4ffc20011f1b68af77efec5a6f3b352248f7bc25 to 24Q1-release

Change-Id: I99a7690e94d8c8c08725a6612c92b02da726eac4
tree: 28f4a7080374fadd9599080be9c3d1d31bf01211
  1. cmake/
  2. doc/
  3. fuzz/
  4. test_cases/
  5. testdata/
  6. abigail_reader.cc
  7. abigail_reader.h
  8. abigail_reader_test.cc
  9. Android.bp
  10. btf_reader.cc
  11. btf_reader.h
  12. catch.cc
  13. CMakeLists.txt
  14. comparison.cc
  15. comparison.h
  16. CONTRIBUTING.md
  17. deduplication.cc
  18. deduplication.h
  19. Dockerfile
  20. dwarf_processor.cc
  21. dwarf_processor.h
  22. dwarf_wrappers.cc
  23. dwarf_wrappers.h
  24. elf_loader.cc
  25. elf_loader.h
  26. elf_reader.cc
  27. elf_reader.h
  28. elf_reader_test.cc
  29. equality.h
  30. equality_cache.h
  31. error.h
  32. error_test.cc
  33. fidelity.cc
  34. fidelity.h
  35. file_descriptor.cc
  36. file_descriptor.h
  37. file_descriptor_test.cc
  38. filter.cc
  39. filter.h
  40. filter_test.cc
  41. fingerprint.cc
  42. fingerprint.h
  43. graph.cc
  44. graph.h
  45. hashing.h
  46. input.cc
  47. input.h
  48. LICENSE
  49. METADATA
  50. metrics.cc
  51. metrics.h
  52. metrics_test.cc
  53. MODULE_LICENSE_LLVM
  54. naming.cc
  55. naming.h
  56. order.h
  57. order_test.cc
  58. OWNERS
  59. post_processing.cc
  60. post_processing.h
  61. proto_reader.cc
  62. proto_reader.h
  63. proto_writer.cc
  64. proto_writer.h
  65. reader_options.h
  66. README.md
  67. reporting.cc
  68. reporting.h
  69. reporting_test.cc
  70. scc.h
  71. scc_test.cc
  72. scope.h
  73. stable_hash.cc
  74. stable_hash.h
  75. stg.cc
  76. stg.proto
  77. stgdiff.cc
  78. stgdiff_test.cc
  79. substitution.h
  80. type_normalisation.cc
  81. type_normalisation.h
  82. type_resolution.cc
  83. type_resolution.h
  84. unification.cc
  85. unification.h
README.md

Symbol-Type Graph (STG)

The STG (symbol-type graph) is an ABI representation and this project contains tools for the creation and comparison of such representations.

The ABI extraction tool, stg, emits a native ABI format. Parsers exist for libabigail's XML format, BTF and ELF / DWARF.

The ABI diff tool, stgdiff, supports multiple reporting options.

STG has a versioned native file format. Older formats can be read and rewritten as the latest.

NOTE: STG is under active developement. Tool arguments and behaviour are subject to change.

Getting STG

Distributions

We intend to package STG for major distributions. Currently we have packages as follows:

DistributionPackage
Arch Linux (AUR)stg-git

Source Code

This source code is available at https://android.googlesource.com/platform/external/stg/.

Building from Source

Instructions are included for local and Docker builds.

Dependencies

STG is written in C++20. It is known to compile with GCC 11, Clang 15 or later versions.

DependencyDebianRedHat
buildcmakecmake
ELF, BTFlibelf-develfutils-devel
DWARFlibdw-develfutils-devel
XMLlibxml2-devlibxml2-devel
BTFlinux-libc-devkernel-headers
native formatlibprotobuf-devprotobuf-devel
native formatprotobuf-compilerprotobuf-compiler
allocator[^1]libjemalloc-devjemalloc-devel
catch2[^2]catch2catch2-devel

[^1]: jemalloc is optional, but will likely improve performance. [^2]: catch2 is optional, but required to build the test suite.

Local Build

Build STG using CMake as follows:

$ mkdir build && cd build
$ cmake ..
$ cmake --build . --parallel

Run the STG unit test suite:

$ ctest

Docker Build

A Dockerfile is provided to build a container with the STG tools:

$ docker build -t stg .

And then enter the container:

$ docker run -it stg

Note that the Dockerfile provides only a production image. To use Docker as a development environment, you can comment out everything after the line # second stage.

After that you may bind your development code to the container:

$ docker run -it $PWD:/src -it stg

The source code is added to /src, so when your code is bound you can edit on your host and re-compile in the container.

Contributions

See CONTRIBUTING.md for details.

Contact Information

Please send feedback, questions and bug reports to [email protected].