Issue #14464 has been updated by k0kubun (Takashi Kokubun).


>  I'm wondering what is using the /Users/user name/AppData/Local/temp folder, as on my system, all TEMP/TMP env variables are set to different folders.

Now MJIT seems to use the result of rb_w32_system_tmpdir(), not just $TEMP or $TMP.

> If there is anything I can add to the build to help identify the issue, I'll be happy to.

Current status of investigation for this ticket: I've investigated why #test_compile_insn_intern_duparray in test_jit.rb fails. I minimized the reproductive code to be `ruby --disable-gems -e 'p proc { 0.to_s }.call' --jit-wait --jit-min-calls=1`.

As far as I've debugged with gdb, the code crashes because `rb_class_of(FIXNUM(0))`, which is called by `vm_search_method` in `_mjit0`, returns the value of `&rb_cInteger` instead of `rb_cInteger`, and then `Module#to_s` is dispatched for `0.to_s`. As 0 is not Module, it crashes. The `rb_class_of` code in MJIT header looks to properly return `rb_cInteger`. So I have no idea why it returns `&rb_cInteger`.

For those who help me for this issue, it would be helpful to confirm that my above understanding is correct or comment some wrong assumption in it. Thanks.

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

* Author: MSP-Greg (Greg L)
* Status: Assigned
* Priority: Normal
* Assignee: k0kubun (Takashi Kokubun)
* 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

---Files--------------------------------
TestJIT_info_62380.txt (33.4 KB)


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