1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix more assumptions about the read barrier

Browse Source 
This is a continuation of 0130e17a410d60a10e7041ce98748b8de6946971.  We
need to always use the read barrier
This commit is contained in:
Aaron Patterson 2021-01-21 11:19:44 -08:00
parent 871b4612b0
commit 32b7dcfb56
No known key found for this signature in database
GPG Key ID: 953170BCB4FFAFC6
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
gc.c
View File

@ -4489,11 +4489,6 @@ static VALUE gc_move(rb_objspace_t *objspace, VALUE scan, VALUE free);
static void
lock_page_body(rb_objspace_t *objspace, struct heap_page_body *body)
{
/* If this is an explicit compaction (GC.compact), we don't need a read
* barrier, so just return early. */
if (objspace->flags.during_compacting >> 1) {
return;
}
#if defined(_WIN32)
DWORD old_protect;
@ -4511,11 +4506,6 @@ lock_page_body(rb_objspace_t *objspace, struct heap_page_body *body)
static void
unlock_page_body(rb_objspace_t *objspace, struct heap_page_body *body)
{
/* If this is an explicit compaction (GC.compact), we don't need a read
* barrier, so just return early. */
if (objspace->flags.during_compacting >> 1) {
return;
}
#if defined(_WIN32)
DWORD old_protect;