[Bug default/18941] Add a warning option to libabigail tools to report possible DWARF issues

["woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18941

--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
Many of the cases which I think need warnings are more prosaic.

If it comes along a case where the DWARF has been stripped or was never
generated, then most if not all of the ABI verification is not being done. This
should be a higher priority warning. This could also remind people to point the
libabigail utilities toward an external debuginfo file. I would say that this
is a high enough priority that it should be the default unless some --quiet
option is passed on the command line.

A lower priority warning would be a exported function entry point for a
non-static function that exists in ELF but doesn't exist in the available
DWARF. This is important because we need to know the things that we are not yet
examining. I thought the option should be something like -Wunexamined-functions

A similar situation is the one you mention where you have a forward declaration
but no information about the class. -Wunexamined-classes

I think that -Wunions probably should be there too. This would trip if
libabigail found any unions in the DWARF and emit the union's name for manual
verification. I do not recall seeing this in the release notes. We should
probably have a note saying that unions are not examined for ABI compatibility
in the release notes.

And finally because the number of these warnings will likely grow over time we
should probably have something like:
-W which turns on common problems
-Wall which turns on every single warning.

-- 
You are receiving this mail because:
You are on the CC list for the bug.