From cd7f3e81ac4c36e704c2ea5d0ca58d773331d32f Mon Sep 17 00:00:00 2001 From: Nathanael See Date: Tue, 15 Oct 2024 17:24:25 -0700 Subject: [PATCH] fix event tracer usage for shader profiling Summary: Seems there was a breaking change recently which went unnoticed. Building with event tracing turned on for shader profiling uncovers this compile error: ``` error: unknown type name 'EventTracer'; did you mean 'runtime::EventTracer'? 603 | EventTracer* event_tracer = context.event_tracer(); | ^~~~~~~~~~~ | runtime::EventTracer executorch/runtime/core/event_tracer.h:115:7: note: 'runtime::EventTracer' declared here 115 | class EventTracer { | ^ 1 error generated. ``` Differential Revision: D64440795 --- backends/vulkan/runtime/VulkanBackend.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backends/vulkan/runtime/VulkanBackend.cpp b/backends/vulkan/runtime/VulkanBackend.cpp index 559c70bd8b4..19737f57184 100644 --- a/backends/vulkan/runtime/VulkanBackend.cpp +++ b/backends/vulkan/runtime/VulkanBackend.cpp @@ -600,7 +600,7 @@ class VulkanBackend final : public ::executorch::runtime::BackendInterface { } #ifdef ET_EVENT_TRACER_ENABLED - EventTracer* event_tracer = context.event_tracer(); + runtime::EventTracer* event_tracer = context.event_tracer(); compute_graph->context()->querypool().extract_results(); for (const auto& tup : compute_graph->context()->querypool().get_shader_timestamp_data()) {