mirror of
git://sourceware.org/git/libabigail.git
synced 2025-01-18 15:20:45 +00:00
The Git repository of the Libabigail Project
9136c6a639
In the DWARF for C++, it can happens that a virtual constructor leads to several (up to 3) destructor functions that all have the same vtable offset. That vtable offset is the same as the offset of the virtual destructor that the user actually defined in her source code. This patch adds a map data structure to the private data of class_decl. That map associates a vtable offset X to a vector of virtual member functions that have the same vtable offset X. That new map is populated whenever a virtual member function is added to the class. * include/abg-ir.h (class_or_union::virtual_mem_fn_map_type): Define new typedef. (class_decl::get_virtual_mem_fns_map): Declare new accessor. * src/abg-ir.cc (class_decl::priv::virtual_mem_fns_map_): New data member. (class_decl::get_virtual_mem_fns_map): Define new accessor. (fixup_virtual_member_function): Populate the new virtual member functions map. (class_decl::on_canonical_type_set): Sort the virtual member function vectors stored in the new virtual member functions map. (class_decl::add_member_function): Call set_member_function_is_virtual *after* calling set_member_function_vtable_offset because the former updates the virtual function map, so it needs the vtable offset. * src/abg-dwarf-reader.cc (finish_member_function_reading): Likewise. * src/abg-reader.cc (build_class_decl): Likewise. Signed-off-by: Dodji Seketeli <dodji@redhat.com> |
||
---|---|---|
autoconf-archive | ||
bash-completion | ||
doc | ||
include | ||
m4 | ||
scripts | ||
src | ||
tests | ||
tools | ||
.gitignore | ||
abigail.m4 | ||
AUTHORS | ||
ChangeLog | ||
COMMIT-LOG-GUIDELINES | ||
COMPILING | ||
configure.ac | ||
CONTRIBUTING | ||
COPYING | ||
COPYING-GPLV3 | ||
COPYING-LGPLV2 | ||
COPYING-LGPLV3 | ||
default.abignore | ||
gen-changelog.py | ||
install-sh | ||
libabigail.pc.in | ||
ltmain.sh | ||
Makefile.am | ||
NEWS | ||
README | ||
release-text-template.txt | ||
VISIBILITY |
This is the Application Binary Interface Generic Analysis and Instrumentation Library. It aims at constructing, manipulating, serializing and de-serializing ABI-relevant artifacts. The set of artifacts that we are intersted is made of quantities like types, variable, fonctions and declarations of a given library or program. For a given library or program this set of quantities is called an ABI corpus. This library aims at (among other things) providing a way to compare two ABI Corpora (apparently the plural of corpus is copora, heh, that's cool), provide detailed information about their differences, and help build tools to infer interesting conclusions about these differences. You are welcome to contribute to this project after reading the files CONTRIBUTING and COMMIT-LOG-GUIDELINES files in the source tree. Communicating with the maintainers of this project -- including sending patches to be include to the source code -- happens via email at libabigail@sourceware.org.