dart-sdk/runtime/vm/code_entry_kind.h

45 lines
1.6 KiB
C
Raw Normal View History

[vm] Decouple assemblers from runtime. This is the next step towards preventing compiler from directly peeking into runtime and instead interact with runtime through a well defined surface. The goal of the refactoring to locate all places where compiler accesses some runtime information and partion those accesses into two categories: - creating objects in the host runtime (e.g. allocating strings, numbers, etc) during compilation; - accessing properties of the target runtime (e.g. offsets of fields) to embed those into the generated code; This change introduces dart::compiler and dart::compiler::target namespaces. All code in the compiler will gradually be moved into dart::compiler namespace. One of the motivations for this change is to be able to prevent access to globally defined host constants like kWordSize by shadowing them in the dart::compiler namespace. The nested namespace dart::compiler::target hosts all information about target runtime that compiler could access, e.g. compiler::target::kWordSize defines word size of the target which will eventually be made different from the host kWordSize (defined by dart::kWordSize). The API for compiler to runtime interaction is placed into compiler_api.h. Note that we still permit runtime to access compiler internals directly - this is not going to be decoupled as part of this work. Issue https://github.com/dart-lang/sdk/issues/31709 Change-Id: If4396d295879391becfa6c38d4802bbff81f5b20 Reviewed-on: https://dart-review.googlesource.com/c/90242 Commit-Queue: Vyacheslav Egorov <vegorov@google.com> Reviewed-by: Martin Kustermann <kustermann@google.com>
2019-01-25 16:45:13 +00:00
// Copyright (c) 2019, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.
#ifndef RUNTIME_VM_CODE_ENTRY_KIND_H_
#define RUNTIME_VM_CODE_ENTRY_KIND_H_
namespace dart {
// Compiled functions might have several different entry points, which either
// perform additional checking on entry into the function or skip some of the
// checks normally performed on the entry.
//
// Which checks are performed and skipped depend on the function and VM mode.
enum class CodeEntryKind {
// Normal entry into the function.
//
// Usually such entries perform type checks for all parameters which are not
// guaranteed to be type checked on the callee side. This can happen if
// parameter type depends on the type parameter of an enclosing class.
kNormal,
// Unchecked entry into the function.
//
// These entries usually skip most of the type checks that normal entries
// perform and are used when optimizing compiler can prove that those
// checks are not needed at a specific call site.
kUnchecked,
// Monomorphic entry into the function.
//
// In AOT mode we might patch call-site to directly invoke target function,
// which would then validate that it is invoked with the expected type of
// the receiver. This validation is handled by monomorphic entry, which then
// falls through to the normal entry.
kMonomorphic,
// Similar to monomorphic entry but with a fallthrough into unchecked entry.
kMonomorphicUnchecked,
};
} // namespace dart
#endif // RUNTIME_VM_CODE_ENTRY_KIND_H_