diff options
| author | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-10-10 11:55:43 +0900 |
|---|---|---|
| committer | 卜部昌平 <shyouhei@ruby-lang.org> | 2019-10-10 12:07:38 +0900 |
| commit | 9c3153e0da991e1a7df9b4cf91d6830effc79b22 (patch) | |
| tree | 67096a78da04f6592d79f3d81b2c4f7b6b0353a2 /common.mk | |
| parent | 25100c469758dd3676ec608ed27fd89248980666 (diff) | |
allow rb_raise from outside of GVL
Now that allocation routines like ALLOC_N() can raise exceptions
on integer overflows. This is a problem when the calling thread
has no GVL. Memory allocations has been allowed without it, but
can still fail.
Let's just relax rb_raise's restriction so that we can call it
with or without GVL. With GVL the behaviour is unchanged. With
no GVL, wait for it.
Also, integer overflows can theoretically occur during GC when
we expand the object space. We cannot do so much then. Call
rb_memerror and let that routine abort the process.
Diffstat (limited to 'common.mk')
| -rw-r--r-- | common.mk | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1942,6 +1942,7 @@ error.$(OBJEXT): $(CCAN_DIR)/list/list.h error.$(OBJEXT): $(CCAN_DIR)/str/str.h error.$(OBJEXT): $(hdrdir)/ruby.h error.$(OBJEXT): $(hdrdir)/ruby/ruby.h +error.$(OBJEXT): $(hdrdir)/ruby/thread.h error.$(OBJEXT): {$(VPATH)}assert.h error.$(OBJEXT): {$(VPATH)}config.h error.$(OBJEXT): {$(VPATH)}defines.h |