[#79914] [Ruby trunk Bug#13282] opt_str_freeze does not always dedupe — normalperson@...
Issue #13282 has been reported by Eric Wong.
4 messages
2017/03/05
[#80140] [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus) — shyouhei@...
Issue #13295 has been updated by shyouhei (Shyouhei Urabe).
5 messages
2017/03/13
[#80362] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— Eric Wong <normalperson@...>
2017/03/26
shyouhei@ruby-lang.org wrote:
[#80368] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— SASADA Koichi <ko1@...>
2017/03/27
On 2017/03/26 15:16, Eric Wong wrote:
[#80205] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint — Eric Wong <normalperson@...>
duerst@ruby-lang.org wrote:
4 messages
2017/03/17
[#80213] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint
— Martin J. Dürst <duerst@...>
2017/03/17
Hello Eric,
[#80290] [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch — normalperson@...
Issue #13355 has been reported by normalperson (Eric Wong).
4 messages
2017/03/23
[#80410] Re: [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch
— Eric Wong <normalperson@...>
2017/03/27
normalperson@yhbt.net wrote:
[#80415] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
5 messages
2017/03/28
[#80488] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
4 messages
2017/03/29
[ruby-core:79958] [Ruby trunk Bug#13288] mingw issues with 57789
From:
Greg.mpls@...
Date:
2017-03-07 22:03:12 UTC
List:
ruby-core #79958
Issue #13288 has been updated by Greg L. Shyouhei, Not a good day so far. A couple rev's of i686 built, responded to -v, but test-all is a mess. Spent some time revising my build code and looking around libffi. Testing 57788 did not yield results similar to what I recall seeing with i686 in the past. MSYS2 had some updates recently, so will soon try to check those. Mostly on i686 today. Reminder, yesterday, after MSYS2 updates, got the following (which is a good result) ``` 16615 tests, 2227473 assertions, 10 failures, 4 errors, 150 skips ruby -v: ruby 2.5.0dev (2017-03-06 trunk 57788) [x64-mingw32] ``` Hence, with current MSYS2/mingw system: x64 57788 and prior builds fine i686 builds have issues compared to the last good data I have: ``` 17074 tests, 4982778 assertions, 12 failures, 9 errors, 147 skips ruby -v: ruby 2.5.0dev (2017-03-01 trunk 57712) [i386-mingw32] ``` Question - the results I posted in #7. Do they indicate the SEGV is in libffi-6.dll? I assume it could also be caused by fiddle.so. Back when I was working on seeing if gdbm 1.12 would work with ruby (don't think so), I was comparing patches between MSYS2, cygwin, and ruby. With libffi, I found the following: [mingw fix_return_size.patch](https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-libffi/fix_return_size.patch) [cygwin 3.2.1-win64-rewrite.patch](https://github.com/cygwinports/libffi/blob/master/3.2.1-win64-rewrite.patch) [ruby libffi-3.2.1-mswin.patch](https://github.com/ruby/ruby/blob/trunk/ext/fiddle/win32/libffi-3.2.1-mswin.patch) No idea whether it's applicable... ---------------------------------------- Bug #13288: mingw issues with 57789 https://bugs.ruby-lang.org/issues/13288#change-63383 * Author: Greg L * Status: Assigned * Priority: Normal * Assignee: Shyouhei Urabe * Target version: * ruby -v: ruby 2.5.0dev (2017-03-06 trunk 57789) [x64-mingw32] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- I have been building trunk with mingw/MSYS2 for a few months. I also created packages using OpenSSL 1.1.0e and gdbm 1.10. Yesterday, I build 57782 with no major issues. Today, when I built 57789 (this commit) I had a segfault in the test-all section. the build.log was fine, and it responds to ruby -v, but I haven't tested further. I built 57782 and 57788 with no major issues. I built 57789 again, and again, the segfault occurred. The full log is at [x86_64-check.log](https://github.com/MSP-Greg/ruby-makepkg-mingw/blob/master/ruby_seg_fault/x86_64-check.log), also attached. I'm not a c type, so if there's anything else you need or would like me to check, please let me know. ---Files-------------------------------- x86_64-check.log (75 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>