Skip to content

Commit cd7f3e8

Browse files
nathanaelseefacebook-github-bot
authored andcommitted
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
1 parent 3e052a8 commit cd7f3e8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

backends/vulkan/runtime/VulkanBackend.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -600,7 +600,7 @@ class VulkanBackend final : public ::executorch::runtime::BackendInterface {
600600
}
601601

602602
#ifdef ET_EVENT_TRACER_ENABLED
603-
EventTracer* event_tracer = context.event_tracer();
603+
runtime::EventTracer* event_tracer = context.event_tracer();
604604
compute_graph->context()->querypool().extract_results();
605605
for (const auto& tup :
606606
compute_graph->context()->querypool().get_shader_timestamp_data()) {

0 commit comments

Comments
 (0)