From: Dodji Seketeli <dodji@seketeli.org>
To: Giuliano Procida <gprocida@google.com>
Cc: libabigail@sourceware.org, kernel-team@android.com,
maennich@google.com
Subject: Re: [PATCH] abidiff: improve treatment of array types in leaf changes mode
Date: Fri, 04 Dec 2020 12:02:55 +0100 [thread overview]
Message-ID: <865z5hq1eo.fsf@seketeli.org> (raw)
In-Reply-To: <20201203150916.3540551-1-gprocida@google.com> (Giuliano Procida's message of "Thu, 3 Dec 2020 15:09:16 +0000")
Hello Giuliano,
Giuliano Procida <gprocida@google.com> a écrit:
[...]
> diff --git a/src/abg-ir.cc b/src/abg-ir.cc
> index c6f7c13e..b0db9c39 100644
> --- a/src/abg-ir.cc
> +++ b/src/abg-ir.cc
> @@ -23606,7 +23606,7 @@ types_have_similar_structure(const type_base* first,
> || ty1->get_dimension_count() != ty2->get_dimension_count()
> || !types_have_similar_structure(ty1->get_element_type(),
> ty2->get_element_type(),
> - indirect_type))
> + true))
> return false;
>
> return true;
I think this change is correct, thanks for spotting that.
However ...
[...]
> If an array's element type doesn't change name but has some other
> (local) change, then the change should not also be considered local to
> the array type.
I find this comment confusing, even if I think I see what you mean.
A change being local or not, is a concept that is not at the same
logical level as the concept of "type similarity" defined in the comment
of the function types_have_similar_structure. I would say that the type
similarity concept is at a lower logical level. So seeing this comment
that applies to a higher level concept for a change made to something
But I agree that the comments of types_have_similar_structure are
confusing as well.
So I am proposing two patches following this message, for this issue.
One patch amends the the comments for types_have_similar_structure, and
the second one is your patch, with amended comments.
And we can discuss from there as you like.
[...]
Cheers,
--
Dodji
next prev parent reply other threads:[~2020-12-04 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 15:09 Giuliano Procida
2020-12-04 11:02 ` Dodji Seketeli [this message]
2020-12-04 11:05 ` [PATCH 1/2] ir: Add better comments to types_have_similar_structure Dodji Seketeli
2020-12-04 11:07 ` [PATCH 2/2] ir: Arrays are indirect types for type similarity purposes Dodji Seketeli
2020-12-04 14:41 ` [PATCH] abidiff: improve treatment of array types in leaf changes mode Giuliano Procida
2020-12-07 13:24 ` Dodji Seketeli
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=865z5hq1eo.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
/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).