Lines Matching refs:abidiff

36 By default, ``abidiff`` filters harmless changes from the diff report.
48 :ref:`abidiff <abidiff_label>`, :ref:`abipkgdiff <abipkgdiff_label>`
1148 Let's ask :ref:`abidiff <abidiff_label>` which ABI differences it sees
1151 	$ abidiff libtest1-v0.so libtest1-v1.so
1168 So ``abidiff`` reports that the opaque_type's layout has changed
1179 Now to teach ``abidiff`` about this soft contract and have it
1192 Let's now invoke ``abidiff`` on the two versions of the library
1195 	$ abidiff --suppressions test1.suppr libtest1-v0.so libtest1-v1.so
1199 As you can see, ``abidiff`` does not report the change anymore; it
1258 then running ``abidiff`` on these two versions of library yields: ::
1260 	$ abidiff libtest3-v0.so libtest3-v1.so
1277 That is, ``abidiff`` shows us the two changes, even though we (the
1282 tells abidiff to filter out change reports about adding a data
1294 Now running ``abidiff`` with this suppression specification yields: ::
1296 	$ ../build/tools/abidiff --suppressions test3-1.suppr libtest3-v0.so libtest3-v1.so
1380 When we invoke ``abidiff`` on the object files resulting from the
1383 	$ abidiff widget-v0.o widget-v1.o
1402 I guess a little bit of explaining is due here.  ``abidiff``
1410 ``struct widget`` through a reference.  But then ``abidiff``
1421 That is why ``abidiff`` tells us about the impact that the change
1432 would like to go tell abidiff to suppress reports about this
1450 Invoking ``abidiff`` on ``widget-v0.o`` and ``widget-v1.o`` with
1453 	$ abidiff --suppressions widget.suppr widget-v0.o widget-v1.o
1594 Let's look at the output of ``abidiff``: ::
1596 	 $ abidiff libtest2-v0.so libtest2-v1.so 
1629 Let's tell ``abidiff`` to avoid showing us the differences on the
1643 And then let's invoke ``abidiff`` with the suppression
1646   $ ../build/tools/abidiff --suppressions libtest2.suppr libtest2-v0.so libtest2-v1.so 
1670   $ ../build/tools/abidiff --suppressions libtest2-1.suppr libtest2-v0.so libtest2-v1.so