[ruby-core:87265] [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).


@k0kubun,

> Thanks for letting me know that


Not being a c type, it's the least I can do.  I often feel like a dumb rock, as I can identify issues, but I can't fix them...

FYI, as of:
```
ruby 2.6.0dev (2018-05-27 trunk 63508) [x64-mingw32]
```

I re-enabled MJIT in ruby-loco, and the build passed.  I've got quite a bit of logging for it, so -

When parallel testing ran, `TestJIT#test_compile_insn_opt_aset` failed at (I believe) the second assert.  It passed three asserts on the retry.

Thanks again for your work on JIT, 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-72254

* Author: MSP-Greg (Greg L)
* Status: Closed
* 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: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>