From: ko1@... Date: 2017-06-09T04:35:45+00:00 Subject: [ruby-core:81627] [Ruby trunk Feature#13637] [PATCH] tool/runruby.rb: test with smallest possible machine stack Issue #13637 has been updated by ko1 (Koichi Sasada). I missed this ticket. I wonder there are no failures on CI. Do you mean that we shouldn't use recursive call which can increase machine stack on `Thread` and `Fiber` in our tests? Now, we don't have such tests (so that we don't have failures/errors) but it is possible. I agree that we should consider about machine stack size, but I'm not sure this approach is correct (at least now it seems no problem). Or if we need to introduce such recursive calls, we remove this restriction? Thanks, Koichi ---------------------------------------- Feature #13637: [PATCH] tool/runruby.rb: test with smallest possible machine stack https://bugs.ruby-lang.org/issues/13637#change-65324 * Author: normalperson (Eric Wong) * Status: Closed * Priority: Normal * Assignee: * Target version: ---------------------------------------- Lets ensure none of our C functions use too much stack space and fix all excessive stack usage before releasing the next version. Reducing C stack usage should reduce conservative GC scanning time and improve performance. Hopefully there are no objections; I will commit in a few days. If there are platform-dependent CI failures; excessive stack usage should be fixed; rather than increasing minimum values or removing these envs from testing. ---Files-------------------------------- 0001-tool-runruby.rb-test-with-smallest-possible-machine-.patch (1.09 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: