drgn/libdrgn/.gitignore

*.la
*.lo
*.o
.deps/
.dirstamp
.libs/
/Makefile
/Makefile.in
/aclocal.m4
/autom4te.cache
/config.log
/config.status
/configure
/html
/libtool
/python/constants.c
/python/docstrings.c
Rewrite drgn core in C The current mixed Python/C implementation works well, but it has a couple of important limitations: - It's too slow for some common use cases, like iterating over large data structures. - It can't be reused in utilities written in other languages. This replaces the internals with a new library written in C, libdrgn. It includes Python bindings with mostly the same public interface as before, with some important improvements: - Types are now represented by a single Type class rather than the messy polymorphism in the Python implementation. - Qualifiers are a bitmask instead of a set of strings. - Bit fields are not considered a separate type. - The lvalue/rvalue terminology is replaced with reference/value. - Structure, union, and array values are better supported. - Function objects are supported. - Program distinguishes between lookups of variables, constants, and functions. The C rewrite is about 6x as fast as the original Python when using the Python bindings, and about 8x when using the C API directly. Currently, the exposed API in C is fairly conservative. In the future, the memory reader, type index, and object index APIs will probably be exposed for more flexibility. 2019-03-22 23:27:46 +00:00			`*.la`
			`*.lo`
			`*.o`
			`.deps/`
Build Python bindings with automake I went back and forth on using setuptools or autotools for the Python extension, but I eventually settled on using only setuptools after fighting to get the two to integrate well. However, setuptools is kind of crappy; for one, it rebuilds every source file when rebuilding the extension, which is really annoying for development. automake is a better designed build system overall, so let's use that for the extension. We override the build_ext command to build using autotools and copy things where setuptools expects them. 2019-04-03 19:33:37 +01:00			`.dirstamp`
Rewrite drgn core in C The current mixed Python/C implementation works well, but it has a couple of important limitations: - It's too slow for some common use cases, like iterating over large data structures. - It can't be reused in utilities written in other languages. This replaces the internals with a new library written in C, libdrgn. It includes Python bindings with mostly the same public interface as before, with some important improvements: - Types are now represented by a single Type class rather than the messy polymorphism in the Python implementation. - Qualifiers are a bitmask instead of a set of strings. - Bit fields are not considered a separate type. - The lvalue/rvalue terminology is replaced with reference/value. - Structure, union, and array values are better supported. - Function objects are supported. - Program distinguishes between lookups of variables, constants, and functions. The C rewrite is about 6x as fast as the original Python when using the Python bindings, and about 8x when using the C API directly. Currently, the exposed API in C is fairly conservative. In the future, the memory reader, type index, and object index APIs will probably be exposed for more flexibility. 2019-03-22 23:27:46 +00:00			`.libs/`
			`/Makefile`
			`/Makefile.in`
			`/aclocal.m4`
			`/autom4te.cache`
			`/config.log`
			`/config.status`
			`/configure`
			`/html`
			`/libtool`
Build Python bindings with automake I went back and forth on using setuptools or autotools for the Python extension, but I eventually settled on using only setuptools after fighting to get the two to integrate well. However, setuptools is kind of crappy; for one, it rebuilds every source file when rebuilding the extension, which is really annoying for development. automake is a better designed build system overall, so let's use that for the extension. We override the build_ext command to build using autotools and copy things where setuptools expects them. 2019-04-03 19:33:37 +01:00			`/python/constants.c`
Document with Sphinx drgn has pretty thorough in-program documentation, but it doesn't have a nice overview or introduction to the basic concepts. This commit adds that using Sphinx. In order to avoid documenting everything in two places, the libdrgn bindings have their docstrings generated from the API documentation. The alternative would be to use Sphinx's autodoc extension, but that's not as flexible and would also require building the extension to build the docs. The documentation for the helpers is generated using autodoc and a small custom extension. 2019-04-04 09:27:23 +01:00			`/python/docstrings.c`