Initialize the lowoverhead trace entry points to nop entry points

We update them when we register the thread, so it doesn't impact what we
initialize these values to. They will be updated based on the
lowoverhead trace type when we register the thread. However, since the
expectation is to have nop entry points when there is no trace running
it is good to initialize them with nop entry points to start with.

Bug: 352518093
Test: art/test.py
Change-Id: I931646a7203ccab8cae6e037a763660b61921e3d

1 files changed, 2 insertions, 2 deletions

diff --git a/runtime/arch/arm64/entrypoints_init_arm64.cc b/runtime/arch/arm64/entrypoints_init_arm64.cc
index dbcb2c7273..3292b15503 100644
--- a/runtime/arch/arm64/entrypoints_init_arm64.cc
+++ b/runtime/arch/arm64/entrypoints_init_arm64.cc
@@ -217,8 +217,8 @@ void InitEntryPoints(JniEntryPoints* jpoints,
   if (art_flags::always_enable_profile_code()) {
     // These are used for always-on-tracing, currently only supported on arm64
     // devices.
-    qpoints->SetRecordEntryTraceEvent(art_quick_record_entry_trace_event);
-    qpoints->SetRecordExitTraceEvent(art_quick_record_exit_trace_event);
+    qpoints->SetRecordEntryTraceEvent(art_quick_nop_record_entry_trace_event);
+    qpoints->SetRecordExitTraceEvent(art_quick_nop_record_exit_trace_event);
   }
 }