From 827f36bada85207960500ad37790cee5e0d191eb Mon Sep 17 00:00:00 2001 From: Tim Holy Date: Wed, 31 Aug 2022 15:13:03 -0500 Subject: [PATCH] Disambiguate invalidation types in jl_insert_method_instance SnoopCompile parses the invalidation log to construct a causal chain for each invalidation. It turns out to be necessary to disambiguate invalidation of callers from invalidation of the primary trigger in jl_insert_method_instance. --- src/dump.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/dump.c b/src/dump.c index a52523e56a71f..22369599806ec 100644 --- a/src/dump.c +++ b/src/dump.c @@ -2368,7 +2368,7 @@ static void jl_insert_method_instances(jl_array_t *list) JL_GC_DISABLED } } } - invalidate_backedges(&remove_code_instance_from_validation, caller, world, "jl_insert_method_instance"); + invalidate_backedges(&remove_code_instance_from_validation, caller, world, "jl_insert_method_instance caller"); // The codeinst of this mi haven't yet been removed jl_code_instance_t *codeinst = caller->cache; while (codeinst) {