From 4a99990b36e29f24f2e0cb12531fa4de65cce071 Mon Sep 17 00:00:00 2001 From: Maxime Chevalier-Boisvert Date: Thu, 4 Mar 2021 14:13:54 -0500 Subject: [PATCH] Update yjit.md --- doc/yjit.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/yjit.md b/doc/yjit.md index f5b50c3d3d..46356c9583 100644 --- a/doc/yjit.md +++ b/doc/yjit.md @@ -44,7 +44,7 @@ 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` +Once YJIT is built, you can either use `./miniruby` from within your build directory, or switch to the YJIT version of `ruby` by using the `chruby` tool: ``` @@ -52,17 +52,17 @@ chruby ruby-yjit ruby myscript.rb ``` -You can dump statistics about compilation and execution by running uJIT with the `--yjit-stats` command-line option: +You can dump statistics about compilation and execution by running YJIT with the `--yjit-stats` command-line option: ``` -./miniruby --ujit-stats myscript.rb +./miniruby --yjit-stats myscript.rb ``` The machine code generated for a given method can be printed by adding `puts YJIT.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: +The YJIT source code is divided between: - `yjit_asm.c`: x86 in-memory assembler we use to generate machine code - `yjit_asm_tests.c`: tests for the in-memory assembler - `yjit_codegen.c`: logic for translating Ruby bytecode to machine code