thread.c (rb_gc_save_machine_context): don't save the stack pointer
in this function.
(RB_GC_SAVE_MACHINE_CONTEXT): call rb_gc_save_machine_context and
save the stack pointer at caller side.
(rb_thread_schedule_rec): use RB_GC_SAVE_MACHINE_CONTEXT instead of
rb_gc_save_machine_context.
(blocking_region_begin): changed to a macro. use
RB_GC_SAVE_MACHINE_CONTEXT instead of rb_gc_save_machine_context. [ruby-dev:39659]
Added by akr (Akira Tanaka) over 15 years ago
in this function.
(RB_GC_SAVE_MACHINE_CONTEXT): call rb_gc_save_machine_context and
save the stack pointer at caller side.
(rb_thread_schedule_rec): use RB_GC_SAVE_MACHINE_CONTEXT instead of
rb_gc_save_machine_context.
(blocking_region_begin): changed to a macro. use
RB_GC_SAVE_MACHINE_CONTEXT instead of rb_gc_save_machine_context.
[ruby-dev:39659]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@25701 b2dd03c8-39d4-4d8f-98ff-823fe69b080e