[#109095] [Ruby master Misc#18888] Migrate ruby-lang.org mail services to Google Domains and Google Workspace — "shugo (Shugo Maeda)" <noreply@...>
Issue #18888 has been reported by shugo (Shugo Maeda).
16 messages
2022/06/30
[ruby-core:108876] [Ruby master Feature#18824] Drop MinGW support of MJIT
From:
"k0kubun (Takashi Kokubun)" <noreply@...>
Date:
2022-06-13 16:41:40 UTC
List:
ruby-core #108876
Issue #18824 has been updated by k0kubun (Takashi Kokubun). Status changed from Open to Closed Removed in commit:f8502a26990c652a2c3c1131614230fec446ab25 ---------------------------------------- Feature #18824: Drop MinGW support of MJIT https://bugs.ruby-lang.org/issues/18824#change-97957 * Author: k0kubun (Takashi Kokubun) * Status: Closed * Priority: Normal * Target version: 3.2 ---------------------------------------- ## Proposal Stop supporting MJIT on MinGW from Ruby 3.2 ## Motivation Compilers on MinGW behave weirdly and MinGW-specific C code is sometimes required as a workaround. Despite the high maintenance cost, nobody seems to be using MJIT on MinGW. ## Background * I installed Ruby 3.1 with RubyInstaller2, which I believe is the most popular method to install MinGW Ruby, and MJIT didn't work in that environment. * MinGW is known to be very slow at compiling C code. It's improbable that the architecture of MJIT performs well on that platform. * In other platforms, compiling an MJIT-generated .c file to a .so file works fine, but it fails on MinGW without any error message. So we have to compile .c to .o first and then build a .so file, just for MinGW. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>