[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
nobu@ruby-lang.org wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
matz@ruby-lang.org wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85731] [Ruby trunk Feature#3187] Allow dynamic Fiber stack size
From:
jjyruby@...
Date:
2018-02-21 14:41:58 UTC
List:
ruby-core #85731
Issue #3187 has been updated by jjyr (jy j).
How about `Thread.with_configure(stack_size: 1024).new(a: 1, b: 2){}`.
`Thread.with_configure(stack_size: 1024).is_a? Thread::Config`.
ko1 (Koichi Sasada) wrote:
> Hi,
>
> I agree with this proposal. Also add same parameter setting feature for
> Thread.
>
> However, I can't make good API to specify stack (VM and machine) size
> (and other parameters if there are).
>
> There are several proposals.
>
> Type 1: Thread creating argument (ex: `Thread.new(stack_size: 1024)`)
> Type 2: Thread global parameter (ex: `Thread.stack_size = 1024`)
>
> I think Type 2 is not good (to set default value is okay. However it
> conflicts other usage. Typically thread-unsafe).
>
> I also think Type 1 has also problem. If you want to pass keyword
> argument "stack_size" to fiber or thread, it should be conflict.
>
> My idea is creating new Thread (Fiber) class with new parameter:
>
> ```ruby
> MyThread = Thread.new_template(stack_size: 1024)
> MyThread.new{
> ...
> }
>
> # Of course "new_template" is bad name.
> ```
>
> Any ideas?
>
> --
> // SASADA Koichi at atdot dot net
----------------------------------------
Feature #3187: Allow dynamic Fiber stack size
https://bugs.ruby-lang.org/issues/3187#change-70542
* Author: mperham (Mike Perham)
* Status: Feedback
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* Target version:
----------------------------------------
=begin
I'd like a way to increase the size of the Fiber stack dynamically so when my program starts, I can set it to whatever value I need for the code I'm running. 4KB is too easy to run into problems when running recursive code but settling on any arbitrary static value seems pointless to me.
=end
---Files--------------------------------
fiber_stacksize.patch (5.89 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>