From e197d9ca71570c980274ddd2cb6a32af6c00d95e Mon Sep 17 00:00:00 2001
From: Aaron Patterson <tenderlove@ruby-lang.org>
Date: Wed, 25 Sep 2019 14:08:11 -0700
Subject: [PATCH] Execute write barrier instead of adding to array

We can mark everything via the instruction objects, so just execute the
write barrier instead of appending to the array
---
 compile.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/compile.c b/compile.c
index d7c05b2e87..004d38670c 100644
--- a/compile.c
+++ b/compile.c
@@ -579,7 +579,7 @@ static int
 iseq_add_mark_object_compile_time(const rb_iseq_t *iseq, VALUE v)
 {
     if (!SPECIAL_CONST_P(v)) {
-	rb_ary_push(ISEQ_COMPILE_DATA(iseq)->mark_ary, v);
+        RB_OBJ_WRITTEN(iseq, Qundef, v);
     }
     return COMPILE_OK;
 }