From: "hsbt (Hiroshi SHIBATA) via ruby-core" Date: 2023-01-10T03:39:52+00:00 Subject: [ruby-core:111763] [Ruby master Feature#18439] Support YJIT for VC++ Issue #18439 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee changed from maximecb (Maxime Chevalier-Boisvert) to yjit YJIT has been rewrote with rust in Ruby 3.2. Should we close this? ---------------------------------------- Feature #18439: Support YJIT for VC++ https://bugs.ruby-lang.org/issues/18439#change-101167 * Author: usa (Usaku NAKAMURA) * Status: Assigned * Priority: Normal * Assignee: yjit ---------------------------------------- I heard that supporting YJIT for VC++ needs mmap from k0kubun-san, so I implemented tiny mmap emulation on Windows and committed it to master. And, I found we need more changes to actually enabled YJIT for VC++, at least: - YJIT requires `OPT_DIRECT_THREADED_CODE` or `OPT_CALL_THREADED_CODE` in `rb_yjit_compile_iseq()`. Really? - Maybe ABI deffers between VC++ and YJIT's expectation. Can I get support to fix above? -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/