Bug 27019

Summary: BUILD metabug
Product: libabigail Reporter: Ben Woodard <woodard>
Component: defaultAssignee: Dodji Seketeli <dodji>
Status: NEW ---    
Severity: normal CC: libabigail, mcermak, sochat1
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Host: Target:
Build: Last reconfirmed:
Bug Depends on: 27208, 27332, 27334, 27514, 28025, 28515, 28641, 28642, 28664, 28675, 28775, 29008, 29013, 29303, 29331, 29332, 22429, 26992, 26993, 27010, 27011, 27012, 27013, 27085, 27086, 27325, 27326, 27327, 27329, 27512, 27513, 27515, 27516, 27517, 27518, 27635, 27726, 27727, 27729, 27963, 27964, 27969, 27970, 28315, 28316, 28324, 28326, 28364, 28365, 28450, 28546, 28669, 28760, 28761, 28773, 28774, 28776, 28976, 29299, 29300, 29302, 29324    
Bug Blocks:    

Description Ben Woodard 2020-12-04 18:46:10 UTC
This is a metabug to track all the bugs stumbled across working on the BUILD project.
Comment 1 Ben Woodard 2021-12-07 01:17:15 UTC
Fundamental requirement:
1) to be able to use the abixml in place of the original ELF object when doing analysis and comparison
  this results in: 
    a) forall ELF_file abidw --abidiff must not report any changes - this has been the majority of the bugs found and fixed so far.
    b) forall libabigail_utilites it must be able to use an abixml file in place of the original ELF object -- e.g. 27635

2) abicompat must give accurate results as much as possible
    a) when evaluating compatibility calls from the libraries back into the application must be considered. 27208 (kind of)
    b) other library dependencies that the app relies on must also be considered when evaluating compatibility 27514
    c) exceptions must be considered 28025
    d) inline functions must be considered
    e) underlinked functions must be considered 27208

3) Objects created by different toolchains should not confuse libabigail when doing comparison. We need tooling that allows us to reliably compare the ABIs of objects created by different tool chains.
    a) const-ness of a function should not be an ABI artifact 28641
    b) vtable positions need to be comparable even with the compiler implies the position rather than explicitly specifying it. 28642
    c) template instantiations need drill down into template value parameters rather than just relying on the template instantiation name 28664