public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@redhat.com>
To: libabigail@sourceware.org
Subject: [PATCH, applied] Bug 30467 - enlightenment fails self check on f38
Date: Mon, 05 Jun 2023 13:18:44 +0200	[thread overview]
Message-ID: <87jzwidunf.fsf@redhat.com> (raw)

Hello,

This is yet another instance of a latent canonical type propagation
issue.  Basically, when reading back a type from ABIXML,
canonicalizing it (in an order that is different from the initial
order in which it has been canonicalized by the DWARF front-end)
yields a different canonical type from the original one computed by
the DWARF front-end, yielding spurious self-comparison changes.

By looking at it a bit closer, I realized the cache of the comparison
results wasn't being cleared upon canceling canonical type
propagation, whenever that canceling occurs.  That leads to some
subsequent comparisons being wrong (albeit fast, heh) because they
rely on cached results that should have been invalidated.

This patch thus clears the type comparison result cache whenever
canonical type propagation canceling occurs.

	* src/abg-ir-priv.h (environment::priv::cancel_ct_propagation):
	Clear the type comparison results cache.

Signed-off-by: Dodji Seketeli <dodji@redhat.com>
---
 src/abg-ir-priv.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/abg-ir-priv.h b/src/abg-ir-priv.h
index 0161017f..fe5a36cf 100644
--- a/src/abg-ir-priv.h
+++ b/src/abg-ir-priv.h
@@ -1053,6 +1053,7 @@ struct environment::priv
     // tentative canonical type that might be later canceled.
     t->priv_->set_does_not_depend_on_recursive_type();
     env.priv_->remove_from_types_with_non_confirmed_propagated_ct(t);
+    env.priv_->clear_type_comparison_results_cache();
   }
 
   /// Clear the propagated canonical type of a given type.
-- 
2.39.1


-- 
		Dodji


                 reply	other threads:[~2023-06-05 11:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87jzwidunf.fsf@redhat.com \
    --to=dodji@redhat.com \
    --cc=libabigail@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).