tree: 2fa9bd45128bb019c2300962b99e74d2e8570c37 [path history] [tgz]
  1. aot/
  2. api/
  3. assembler/
  4. backend/
  5. ffi/
  6. frontend/
  7. jit/
  8. asm_intrinsifier.cc
  9. asm_intrinsifier.h
  10. asm_intrinsifier_arm.cc
  11. asm_intrinsifier_arm64.cc
  12. asm_intrinsifier_ia32.cc
  13. asm_intrinsifier_x64.cc
  14. call_specializer.cc
  15. call_specializer.h
  16. cha.cc
  17. cha.h
  18. cha_test.cc
  19. compiler_pass.cc
  20. compiler_pass.h
  21. compiler_sources.gni
  22. compiler_state.cc
  23. compiler_state.h
  24. graph_intrinsifier.cc
  25. graph_intrinsifier.h
  26. graph_intrinsifier_arm.cc
  27. graph_intrinsifier_arm64.cc
  28. graph_intrinsifier_ia32.cc
  29. graph_intrinsifier_x64.cc
  30. intrinsifier.cc
  31. intrinsifier.h
  32. method_recognizer.cc
  33. method_recognizer.h
  34. offsets_extractor.cc
  35. README.md
  36. recognized_methods_list.h
  37. relocation.cc
  38. relocation.h
  39. runtime_api.cc
  40. runtime_api.h
  41. runtime_offsets_extracted.h
  42. runtime_offsets_list.h
  43. stub_code_compiler.cc
  44. stub_code_compiler.h
  45. stub_code_compiler_arm.cc
  46. stub_code_compiler_arm64.cc
  47. stub_code_compiler_ia32.cc
  48. stub_code_compiler_x64.cc
  49. type_testing_stubs_arm.cc
  50. type_testing_stubs_arm64.cc
  51. type_testing_stubs_x64.cc
  52. write_barrier_elimination.cc
  53. write_barrier_elimination.h
  54. write_barrier_elimination_test.cc
runtime/vm/compiler/README.md

Dart VM Compilation Pipeline

This folder contains Dart VM compilation pipeline.

Compilation pipeline is mainly responsible for converting AST or Kernel AST into IL flow graphs and then generating native code from IL.

It has the following structure:

DirectoryWhat goes there
assembler/Assemblers and disassemblers
backend/IL based compilation backend: optimization passes and architecture specific code generation rules
frontend/Frontends responsible for converting AST into IL
jit/JIT specific passes and compilation pipeline entry points
aot/AOT specific passes and compilation pipeline entry points
.Shared code or code without clear designation.

Currently there are no layering restrictions and components from different subfolders can reference each other.