[前][次][番号順一覧][スレッド一覧]

ruby-changes:73337

From: Takashi <ko1@a...>
Date: Wed, 31 Aug 2022 09:08:11 +0900 (JST)
Subject: [ruby-changes:73337] 221a523683 (master): Put a documentation about MJIT [ci skip]

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

From 221a52368362a16570f5025a9a055534a49bfbe9 Mon Sep 17 00:00:00 2001
From: Takashi Kokubun <takashikkbn@g...>
Date: Tue, 30 Aug 2022 17:07:27 -0700
Subject: Put a documentation about MJIT [ci skip]

---
 doc/mjit/mjit.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 doc/mjit/mjit.md

diff --git a/doc/mjit/mjit.md b/doc/mjit/mjit.md
new file mode 100644
index 0000000000..4d345a95ae
--- /dev/null
+++ b/doc/mjit/mjit.md
@@ -0,0 +1,16 @@ https://github.com/ruby/ruby/blob/trunk/doc/mjit/mjit.md#L1
+# MJIT
+
+Here are some tips that might be useful when you work on MJIT:
+
+## Always run make install
+
+Always run `make install` before running MJIT. It could easily cause a SEGV if you don't.
+MJIT looks for the installed header for security reasons.
+
+## --mjit-debug vs --mjit-debug=-ggdb3
+
+`--mjit-debug=[flags]` allows you to specify arbitrary flags while keeping other compiler flags like `-O3`,
+which is useful for profiling benchmarks.
+
+`--mjit-debug` alone, on the other hand, disables `-O3` and adds debug flags.
+If you're debugging MJIT, what you need to use is not `--mjit-debug=-ggdb3` but `--mjit-debug`.
-- 
cgit v1.2.1


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

[前][次][番号順一覧][スレッド一覧]