public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Giuliano Procida <gprocida@google.com>
To: dodji at redhat dot com <sourceware-bugzilla@sourceware.org>
Cc: Giuliano Procida via Libabigail <libabigail@sourceware.org>
Subject: Re: [Bug default/27569] abidiff misses a function parameter addition
Date: Thu, 25 Mar 2021 16:33:48 +0000	[thread overview]
Message-ID: <CAGvU0H=QwALiVtwQzhMxFEVWJMmPhPxPM0SQ1vA4BRW5LVn56g@mail.gmail.com> (raw)
In-Reply-To: <bug-27569-9487-2V4cCymsHn@http.sourceware.org/bugzilla/>

Hi.

On Thu, 25 Mar 2021 at 11:22, dodji at redhat dot com via Libabigail <
libabigail@sourceware.org> wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=27569
>
> --- Comment #7 from dodji at redhat dot com ---
> I have posted this tentative patch
> https://sourceware.org/pipermail/libabigail/2021q1/003301.html.
>
> Could you please try it in your environment to see if it addresses the
> issue
> and review it?
>
>
I had a quick look. It seems to do the trick.

I don't think you need to include new test files as at least one existing
test is affected by the change.

A couple of questions:

Can any other function level changes be missed? I'm guessing not, from
looking at the XML attributes on a function-decl.

In the bug, I wrote:

I also think the only reason problems have not been noticed before is that
is_filtered_out contains the suspicious-looking:

  if (category == NO_CHANGE_CATEGORY)
    return false;

If I remove this line and re-run tests, some other diffs disappear, such as:

---
/usr/local/google/home/gprocida/android/libabigail/build/../tests/data/test-diff-suppr/test10-changed-parm-c-report-0.txt
  2021-02-03 10:29:34.846116830 +0000
+++
/usr/local/google/home/gprocida/android/libabigail/build/tests/output/test-diff-suppr/test10-changed-parm-c-report-0.txt
   2021-03-25 16:28:56.472979039 +0000
@@ -1,16 +1,3 @@
-Functions changes summary: 0 Removed, 1 Changed, 0 Added function
+Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added
function
 Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

-1 function with some indirect sub-type change:
-
-  [C] 'function int foo(int, int)' has some indirect sub-type changes:
-    return type changed:
-      type name changed from 'int' to 'float'
-      type size hasn't changed
-    parameter 1 of type 'int' changed:
-      type name changed from 'int' to 'float'
-      type size hasn't changed
-    parameter 2 of type 'int' changed:
-      type name changed from 'int' to 'float'
-      type size hasn't changed
-

Does this mean you are also missing a category for "has changed to a
different type"? Or is that somehow the residual meaning
of NO_CHANGE_CATEGORY?

Thanks in advance.
>
>
You're welcome.


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

  reply	other threads:[~2021-03-25 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 15:21 [Bug default/27569] New: " gprocida+abigail at google dot com
2021-03-15 13:17 ` [Bug default/27569] " gprocida+abigail at google dot com
2021-03-15 13:24 ` gprocida+abigail at google dot com
2021-03-24 17:10 ` dodji at redhat dot com
2021-03-24 17:18 ` gprocida+abigail at google dot com
2021-03-24 23:58 ` gprocida+abigail at google dot com
2021-03-25 10:07 ` dodji at redhat dot com
2021-03-25 11:22 ` dodji at redhat dot com
2021-03-25 16:33   ` Giuliano Procida [this message]
2021-03-26 11:25     ` Dodji Seketeli
2021-03-25 16:34 ` gprocida at google dot com
2021-03-26 11:26 ` dodji at seketeli dot org
2021-03-29 17:55 ` dodji at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGvU0H=QwALiVtwQzhMxFEVWJMmPhPxPM0SQ1vA4BRW5LVn56g@mail.gmail.com' \
    --to=gprocida@google.com \
    --cc=libabigail@sourceware.org \
    --cc=sourceware-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).