Issue #13637 has been updated by ReiOdaira (Rei Odaira).


Thanks for the patch.  Unfortunately, it did not solve the problem.  Looks like this test does not call `nogvl_copy_stream_read_write()` but instead calls `copy_stream_fallback_body()`. As far as I read the code, there is no large array stack-allocated on that path...?

----------------------------------------
Feature #13637: [PATCH] tool/runruby.rb: test with smallest possible machine stack
https://bugs.ruby-lang.org/issues/13637#change-65946

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>