Correctly handle non-invokable methods in InitializeMethodsCode
Non-invokable methods were handled correctly when there is no
instrumentation but it was not obvious or explicitly handled. For ex: we
could still install AOT code but we never pass AOT code for
non-invokable methods. When instrumentation was enabled, non-invokable
methods weren't handled correctly. This CL makes the handling explicit
by initializing the entrypoint to QuickToInterpreterEntryBridge.
Bug: 206029744
Test: art/testrunner.py -t 2240-tracing-non-invokable-method
Change-Id: Idf2e95e29791d0e4244afa5dfe36e5b78649853c
diff --git a/test/2240-tracing-non-invokable-method/run b/test/2240-tracing-non-invokable-method/run
new file mode 100755
index 0000000..1f7edfc
--- /dev/null
+++ b/test/2240-tracing-non-invokable-method/run
@@ -0,0 +1,17 @@
+#!/bin/bash
+#
+# Copyright 2022 The Android Open Source Project
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+./default-run "$@" --runtime-option -Xmethod-trace --runtime-option -Xmethod-trace-file:/dev/null