Issue #19325 has been updated by nobu (Nobuyoshi Nakada). Assignee set to k0kubun (Takashi Kokubun) Backport changed from 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN to 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: UNKNOWN

With rust having first class windows support and threading support, is there a reason why yjit is not able to work on windows?

Whether the tool (rustc) used to write a (YJIT) compiler supports a platform and whether the compiler supports the platform are completely unrelated. YJIT needs to emit code with obeying the convention for each platform, rust doesn't do it automatically. In contrary, even if the former is not true, the latter can be possible; that is called a cross-compiler. ---------------------------------------- Bug #19325: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-101161 * Author: dsisnero (Dominic Sisneros) * Status: Open * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: UNKNOWN ---------------------------------------- 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/

Issue #19325 has been updated by matz (Yukihiro Matsumoto). The reason Windows being second class is not lack of interest but lack of contributors with extensive experience with (non WSL) Windows platform. Any contributors? I understand your frustration, but complaining does not improve the situation, unfortunately. We need contribution. Matz. ---------------------------------------- Bug #19325: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-101166 * Author: dsisnero (Dominic Sisneros) * Status: Assigned * Priority: Normal * Assignee: yjit * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: UNKNOWN ---------------------------------------- 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/

Issue #19325 has been updated by mame (Yusuke Endoh). Tracker changed from Bug to Feature Backport deleted (2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN) Sorry, not intended to change the tracker ---------------------------------------- Feature #19325: YJIT: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-101174 * Author: dsisnero (Dominic Sisneros) * Status: Assigned * Priority: Normal * Assignee: yjit ---------------------------------------- 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/

Issue #19325 has been updated by aidog (Andi Idogawa). Hello everyone! First, let me thank you for all your work! Ruby on Windows has helped me a lot over the years. Gems with C extensions used sometimes fail to install, but nowadays it works. Ruby Installer with MSYS2 actually works quite well. Of course, it would be nice, if MSYS2 wasn't necessary, but I believe most users care the most that for example **gem install sqlite3** just works. I'm a ruby programmer without much C experience, but as a challenge, I tried to figure out how to debug the ruby source code on windows. I think the easiest way to build is to use ruby-loco[1]. I managed to debug and step through the code, but it took me a few days. While I cannot help with development, wouldn't it be good to make it easier for others to build and debug ruby on windows, so a lot more people could easily help? By the way, I started this project, because require takes longer on windows[2]. I found a lot of good work over the years to make FileIO on windows faster, but if you look at the linked CSV file [3] you will see a lot of syscalls (0.5 seconds long for require 'tzinfo'). I couldn't figure out if it's in the c code (winnt_stat should be cached?) or if it is actually rubygems that does unnecessary things. If I remove all the duplicate syscalls with the (seemingly) same result from the file, it would only take 0.06 seconds... wow! If we improve this, maybe more people will use ruby to make windows GUI applications, because they will start faster. Users don't need to install ruby, because there is ocra [4]. Of course, if we also get YJIT that would be even better. Thanks again everyone! [1] https://github.com/MSP-Greg/ruby-loco/ [2] https://github.com/oneclick/rubyinstaller2/issues/328 [3] https://github.com/oneclick/rubyinstaller2/files/10370934/Logfile.CSV [4] https://github.com/larsch/ocra ---------------------------------------- Feature #19325: YJIT: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-101232 * Author: dsisnero (Dominic Sisneros) * Status: Assigned * Priority: Normal * Assignee: yjit ---------------------------------------- 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/

Issue #19325 has been updated by tamaron (Raiki Tamura). Hello, any progress here? I am very new to the Ruby community but interested in working on this. ---------------------------------------- Feature #19325: YJIT: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-104077 * Author: dsisnero (Dominic Sisneros) * Status: Assigned * Priority: Normal * Assignee: yjit ---------------------------------------- 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/

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/

Issue #19325 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Assigned to Closed Closing as a duplicate of #18439. YJIT on mswin is waiting for review at https://github.com/ruby/ruby/pull/19114. ---------------------------------------- Feature #19325: YJIT: Windows support lacking. https://bugs.ruby-lang.org/issues/19325#change-119248 * Author: dsisnero (Dominic Sisneros) * Status: Closed * 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/