From: Greg.mpls@... Date: 2018-05-22T22:43:54+00:00 Subject: [ruby-core:87227] [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 MSP-Greg (Greg L). ruby -v changed from ruby 2.6.0dev (2018-02-11 trunk 62371) [x64-mingw32] to ruby 2.6.0dev (2018-05-23 trunk 63492) [x64-mingw32] @k0kubun, Just ran with 63492, all passed with 5 skips, partial log: ``` 1) Skipped: TestJIT#test_compile_insn_getblockparamproxy [C:/Greg/GitHub/ruby/test/ruby/test_jit.rb:89]: support this in mjit_compile 2) Skipped: TestJIT#test_compile_insn_opt_call_c_function [C:/Greg/GitHub/ruby/test/ruby/test_jit.rb:523]: support this in opt_call_c_function (low priority) 3) Skipped: TestJIT#test_compile_insn_reput [C:/Greg/GitHub/ruby/test/ruby/test_jit.rb:246]: write test 4) Skipped: TestJIT#test_compile_insn_tracecoverage [C:/Greg/GitHub/ruby/test/ruby/test_jit.rb:277]: write test 5) Skipped: TestJIT#test_compile_insn_defineclass [C:/Greg/GitHub/ruby/test/ruby/test_jit.rb:281]: support this in mjit_compile (low priority) Finished tests in 226.166094s, 0.3228 tests/s, 1.9808 assertions/s. 73 tests, 448 assertions, 0 failures, 0 errors, 5 skips ruby -v: ruby 2.6.0dev (2018-05-23 trunk 63492) [x64-mingw32] ``` Thanks for your work on this, Greg ---------------------------------------- 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-72216 * Author: MSP-Greg (Greg L) * Status: Assigned * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Target version: * ruby -v: ruby 2.6.0dev (2018-05-23 trunk 63492) [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 ---Files-------------------------------- TestJIT_info_62380.txt (33.4 KB) MJIT-MinGW-63333.txt (28.7 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: