[#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:80259] [Ruby trunk Bug#13338] MinGW SEGV in test/ruby/test_keyword.rb svn 58034, ok in svn 58021.
From:
Greg.mpls@...
Date:
2017-03-21 00:14:31 UTC
List:
ruby-core #80259
Issue #13338 has been updated by MSP-Greg (Greg L). I recently changed my build system from a dual core notebook to a quad core desktop. On the notebook, I never recall a SEGV that occurred in test-all that did not occur in the test pulled from the framework. On my desktop, I changed the j parameter in the make test-all call to `j2` from the notebook's `j1`. I'm now seeing tests that fail or SEGV in test-all, but not when run separately. Hence, I have more testing to do. Sorry. I should have a better understanding in a few hours; I'll post results. ---------------------------------------- Bug #13338: MinGW SEGV in test/ruby/test_keyword.rb svn 58034, ok in svn 58021. https://bugs.ruby-lang.org/issues/13338#change-63696 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.5.0dev (2017-03-20 trunk 58034) [x64-mingw32] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- In a MinGW / MSYS2 64 bit build, the following line generates a SEGV in svn 58034 [test/ruby/test_keyword.rb:L373](https://github.com/ruby/ruby/blob/57d6dd5a461202f9824c3d1b8d3e5304aca2d21c/test/ruby/test_keyword.rb#L373). With 373 commented out, all tests in the file pass. This does not occur in svn 58021 for either 32 or 64. Haven't built 32 bit in 58034 yet. No SEGV info is generated, either in test-all or running the test after build... -- 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>