[ruby-core:111758] [Ruby master Bug#19325] Windows support lacking.

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 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/