https://git.ruby-lang.org/ruby.git/commit/?id=f2b170b01d

From f2b170b01d36f3cab2671cc575e75c916bc95bfa Mon Sep 17 00:00:00 2001
From: Maxime Chevalier-Boisvert <maximechevalierb@g...>
Date: Thu, 4 Mar 2021 13:35:58 -0500
Subject: Update and rename ujit.md to yjit.md

---
 doc/ujit.md | 82 -------------------------------------------------------------
 doc/yjit.md | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 82 insertions(+), 82 deletions(-)
 delete mode 100644 doc/ujit.md
 create mode 100644 doc/yjit.md

diff --git a/doc/ujit.md b/doc/ujit.md
deleted file mode 100644
index a96883943b..0000000000
--- a/doc/ujit.md
+++ /dev/null
@@ -1,82 +0,0 @@ https://github.com/ruby/ruby/blob/trunk/#L0
-MicroJIT (uJIT)
-===============
-
-**DISCLAIMER: Please note that this project is in early stages of development. It is very much a work in progress, it may cause your software to crash, and current performance results are likely to leave you feeling underwhelmed.**
-
-MicroJIT is a lightweight, minimalistic Ruby JIT built inside the CRuby/MRI binary.
-It lazily compiles code using a Basic Block Versioning (BBV) architecture. The target use case is that of servers running
-Ruby on Rails, an area where CRuby's MJIT has not yet managed to deliver speedups. 
-To simplify development, we currently support only MacOS and Linux on x86-64, but an ARM64 backend
-is part of future plans.
-This project is open source and falls under the same license as CRuby.
-
-If you would like to learn more about BBV, there are two published papers, and associated conference talks:
-- [Simple and Effective Type Check Removal through Lazy Basic Block Versioning](https://arxiv.org/pdf/1411.0352.pdf) ([ECOOP 2015 talk](https://www.youtube.com/watch?v=S-aHBuoiYE0))
-- [Interprocedural Type Specialization of JavaScript Programs Without Type Analysis](https://drops.dagstuhl.de/opus/volltexte/2016/6101/pdf/LIPIcs-ECOOP-2016-7.pdf) ([ECOOP 2016 talk](https://www.youtube.com/watch?v=sRNBY7Ss97A))
-
-## Installation
-
-Start by cloning the `microjit` branch of the `Shopify/ruby` repository:
-
-```
-git clone https://github.com/Shopify/ruby.git microjit
-cd microjit
-git checkout microjit
-```
-
-The uJIT `ruby` binary can be built with either GCC or Clang. We recommend enabling debug symbols so that assertions are enabled during development as this makes debugging easier. More detailed build instructions are provided in the [Ruby README](https://github.com/ruby/ruby#how-to-compile-and-install).
-
-```
-autoconf
-./configure cppflags=-DRUBY_DEBUG --prefix=$HOME/.rubies/ruby-microjit
-make -j16 install
-```
-
-You can test that uJIT works correctly by running:
-
-```
-# Quick tests found in /bootstraptest
-make btest
-
-# Complete set of tests
-make -j16 test-all
-```
-
-## Usage
-
-Once uJIT is built, you can either use `./miniruby` from within your build directory, or switch to the uJIT version of `ruby`
-by using the `chruby` tool:
-
-```
-chruby ruby-microjit
-ruby myscript.rb
-```
-
-You can dump statistics about compilation and execution by running uJIT with the `--ujit-stats` command-line option:
-
-```
-./miniruby --ujit-stats myscript.rb
-```
-
-The machine code generated for a given method can be printed by adding `puts UJIT.disasm(method(:method_name))` to a Ruby script. Note that no code will be generated if the method is not compiled.
-
-## Source Code Organization
-
-The uJIT source code is divided between:
-- `ujit_asm.c`: x86 in-memory assembler we use to generate machine code
-- `ujit_asm_tests.c`: tests for the in-memory assembler
-- `ujit_codegen.c`: logic for translating Ruby bytecode to machine code
-- `ujit_core.c`: basic block versioning logic, core structure of uJIT
-- `ujit_iface.c`: code uJIT uses to interface with the rest of CRuby
-- `ujit.rb`: `UJIT` module that is exposed to Ruby code
-- `test_asm.sh`: script to compile and run the in-memory assembler tests
-- `vm.inc.erb`: template instruction handler used to hook into the interpreter
-
-The core of CRuby's interpreter logic is found in:
-- `insns.def`: defines Ruby's bytecode instructions
-- `vm_insnshelper.c`: logic used by Ruby's bytecode instructions
-- `vm_exec.c`: Ruby interpreter loop
-
-## Contributing
-
-We welcome open source contributors. If you are interested in contributing to this project, please contact Maxime Chevalier [(@Love2Code) via twitter](https://twitter.com/Love2Code). Suggestions on how to make this readme file more helpful for new contributors are most welcome.
diff --git a/doc/yjit.md b/doc/yjit.md
new file mode 100644
index 0000000000..be9fb8c14b
--- /dev/null
+++ b/doc/yjit.md
@@ -0,0 +1,82 @@ https://github.com/ruby/ruby/blob/trunk/doc/yjit.md#L1
+YJIT - Yet Another Ruby JIT
+===========================
+
+**DISCLAIMER: Please note that this project is in early stages of development. It is very much a work in progress, it may cause your software to crash, and current performance results are likely to leave you feeling underwhelmed.**
+
+MicroJIT is a lightweight, minimalistic Ruby JIT built inside the CRuby/MRI binary.
+It lazily compiles code using a Basic Block Versioning (BBV) architecture. The target use case is that of servers running
+Ruby on Rails, an area where CRuby's MJIT has not yet managed to deliver speedups. 
+To simplify development, we currently support only MacOS and Linux on x86-64, but an ARM64 backend
+is part of future plans.
+This project is open source and falls under the same license as CRuby.
+
+If you would like to learn more about BBV, there are two published papers, and associated conference talks:
+- [Simple and Effective Type Check Removal through Lazy Basic Block Versioning](https://arxiv.org/pdf/1411.0352.pdf) ([ECOOP 2015 talk](https://www.youtube.com/watch?v=S-aHBuoiYE0))
+- [Interprocedural Type Specialization of JavaScript Programs Without Type Analysis](https://drops.dagstuhl.de/opus/volltexte/2016/6101/pdf/LIPIcs-ECOOP-2016-7.pdf) ([ECOOP 2016 talk](https://www.youtube.com/watch?v=sRNBY7Ss97A))
+
+## Installation
+
+Start by cloning the `microjit` branch of the `Shopify/ruby` repository:
+
+```
+git clone https://github.com/Shopify/ruby.git microjit
+cd microjit
+git checkout microjit
+```
+
+The uJIT `ruby` binary can be built with either GCC or Clang. We recommend enabling debug symbols so that assertions are enabled during development as this makes debugging easier. More detailed build instructions are provided in the [Ruby README](https://github.com/ruby/ruby#how-to-compile-and-install).
+
+```
+autoconf
+./configure cppflags=-DRUBY_DEBUG --prefix=$HOME/.rubies/ruby-microjit
+make -j16 install
+```
+
+You can test that uJIT works correctly by running:
+
+```
+# Quick tests found in /bootstraptest
+make btest
+
+# Complete set of tests
+make -j16 test-all
+```
+
+## Usage
+
+Once uJIT is built, you can either use `./miniruby` from within your build directory, or switch to the uJIT version of `ruby`
+by using the `chruby` tool:
+
+```
+chruby ruby-microjit
+ruby myscript.rb
+```
+
+You can dump statistics about compilation and execution by running uJIT with the `--ujit-stats` command-line option:
+
+```
+./miniruby --ujit-stats myscript.rb
+```
+
+The machine code generated for a given method can be printed by adding `puts UJIT.disasm(method(:method_name))` to a Ruby script. Note that no code will be generated if the method is not compiled.
+
+## Source Code Organization
+
+The uJIT source code is divided between:
+- `ujit_asm.c`: x86 in-memory assembler we use to generate machine code
+- `ujit_asm_tests.c`: tests for the in-memory assembler
+- `ujit_codegen.c`: logic for translating Ruby bytecode to machine code
+- `ujit_core.c`: basic block versioning logic, core structure of uJIT
+- `ujit_iface.c`: code uJIT uses to interface with the rest of CRuby
+- `ujit.rb`: `UJIT` module that is exposed to Ruby code
+- `test_asm.sh`: script to compile and run the in-memory assembler tests
+- `vm.inc.erb`: template instruction handler used to hook into the interpreter
+
+The core of CRuby's interpreter logic is found in:
+- `insns.def`: defines Ruby's bytecode instructions
+- `vm_insnshelper.c`: logic used by Ruby's bytecode instructions
+- `vm_exec.c`: Ruby interpreter loop
+
+## Contributing
+
+We welcome open source contributors. If you are interested in contributing to this project, please contact Maxime Chevalier [(@Love2Code) via twitter](https://twitter.com/Love2Code). Suggestions on how to make this readme file more helpful for new contributors are most welcome.
-- 
cgit v1.2.1


--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/