<snip> > > --- > > devtools/libabigail.abignore | 5 +++++ > > lib/librte_eal/x86/include/rte_cpuflags.h | 19 +++++++++++++++++++ > > lib/librte_eal/x86/rte_cpuflags.c | 18 ++++++++++++++++++ > > 3 files changed, 42 insertions(+) > > > > diff --git a/devtools/libabigail.abignore > > b/devtools/libabigail.abignore index a59df8f13..045f436fb 100644 > > --- a/devtools/libabigail.abignore > > +++ b/devtools/libabigail.abignore > > Kevin - you still have the surpession. > I am testing locally with 1.7.1, and it doesn't complain when I disable the > supression. > Are you seeing something different? >
Ray, I have re-tested and with libabigail 1.6 and it reports the addition of the flags as an ABI break without the abignore suppression. With the suppression, it will still report changes to existing flags (e.g. inserting a new flag somewhere in the middle) in the enum as an ABI break, as expected. The Travis CI is also based on Ubuntu 18.04 LTS, which uses libabigail 1.2-1. Without the suppression the community Travis CI builds fail on this false positive. -Kevin
