Issue #19325 has been updated by aidog (Andi Idogawa). Hello everyone I'm happy (and surprised) to report that due to the wonders of the current AI age, it became possible to get to experimental yjit support on windows. https://github.com/Largo/ruby/pull/1/changes From what I can see it touches quite a bit of the regular YJIT code, so it needs someone who knows what's going on, but I would have thought it would be more changes than these. As for testing on windows, what I did is to use packer to get a windows vm on a linux server. Then ssh into the windows box using vagrant or regularly through openssh. I can share the setup if there is interest. ---------------------------------------- Feature #19325: YJIT: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-118479 * Author: dsisnero (Dominic Sisneros) * Status: Assigned * Assignee: jit ---------------------------------------- Ruby's support on windows has always been second class. With some of the recent decisions, windows support is falling even more behind. Recent developments in mjit and yjit that exclude windows are two glaring issues that should be corrected. Googling 'percent of windows vs other operating systems' and it shows windows has a share of 76%. Ceding that users to python and other programming languages has to be one of the reasons python continues get more market share from ruby. With rust having first class windows support and threading support, is there a reason why yjit is not able to work on windows? Also, windows compiler support has matured enough and vcpkg support has evolved enough that it seems it should be possible to finally get a ruby version without having to use msys2. Even Crystal language has a version that runs on windows without needing msys2. -- https://bugs.ruby-lang.org/