From: takashikkbn@... Date: 2018-02-12T01:33:03+00:00 Subject: [ruby-core:85504] [Ruby trunk Bug#14464] MJIT & MinGW / gcc 7.3.0 seemed ok as of 62337, fail or skip after Issue #14464 has been updated by k0kubun (Takashi Kokubun). It seems that all JIT compilations started to fail from r62340, and I fixed it on r62375. Now the tests won't be skipped on MinGW builds. For now, I recommend to specify environment variable RUBY_FORCE_TEST_JIT=1 when running test-all. After r62375, JIT infrastructure seems working. But some tests in test_jit.rb is failing. The test failure seems to be caused by pointing to invalid address in generated code. As Linux builds are perfectly working, probably it's caused by difference between size of variable types and wrong casting. We need deeper investigation for it... ---------------------------------------- Bug #14464: MJIT & MinGW / gcc 7.3.0 seemed ok as of 62337, fail or skip after https://bugs.ruby-lang.org/issues/14464#change-70297 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-02-11 trunk 62371) [x64-mingw32] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- First of all, a thank you to those working on MJIT. At least three builds of ruby-loco MinGW passed the MJIT tests (62327, 62331, 62337), but after that, the tests have either failed or skipped. First fail was at 62341. The most recent build (2018-02-11 trunk 62371), skipped with no timeout error in `jit_supported?` I haven't looked at patching `test_jit.rb` to see if I can get more info. I don't know if this is a MinGW issue or a gcc 7.3.0 issue, but, given that it did work for a few builds, I would appreciate it if someone could look into it. Anything I can help with, I'm happy to. Thanks, Greg -- https://bugs.ruby-lang.org/ Unsubscribe: