Skip to content

Commit 28e0af5

Browse files
committed
Do not indicate location with this on unsafe field access to work around potential compiler bug
There seems to be a Graal compiler bug, at least that's what a ZipPy commit indicates. And this change here also seems to fix the issues with the Bounce benchmark. Signed-off-by: Stefan Marr <git@stefan-marr.de>
1 parent b9bf1ec commit 28e0af5

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/som/interpreter/nodes/FieldAccessor.java

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,13 +49,15 @@ private static final class DirectStoreAccessor extends FieldAccessor {
4949

5050
@Override
5151
public Object read(final SObject self) {
52-
return CompilerDirectives.unsafeGetObject(self, fieldOffset, true, this);
52+
//return CompilerDirectives.unsafeGetObject(self, fieldOffset, true, this);
53+
return CompilerDirectives.unsafeGetObject(self, fieldOffset, true, null);
5354
}
5455

5556

5657
@Override
5758
public void write(final SObject self, final Object value) {
58-
CompilerDirectives.unsafePutObject(self, fieldOffset, value, this);
59+
// CompilerDirectives.unsafePutObject(self, fieldOffset, value, this);
60+
CompilerDirectives.unsafePutObject(self, fieldOffset, value, null);
5961
}
6062
}
6163
}

0 commit comments

Comments
 (0)