Displaying 2 results from an estimated 2 matches for "ofield".
Did you mean:
field
2016 Jul 12
2
RFC: Strong GC References in LLVM
...ce into a fluctuating GCREF
>> (which is not allowed).
>
> I think the original code is unspecified, maybe undefined at the
point of %val_i’s use.
I'd say that would depend on what use. For instance, say we have:
class A {
long lField; // Offset 16
}
class B {
Object oField; // Offset 16
}
void h(B b) {
Object o = b;
hC = b.oField.hashCode();
if (o instanceof A) {
print(((A)o).lField + 20);
}
}
it is reasonable to optimize "h" to:
void h(i8* b) {
GCREF o = *(b + 16)
long l = *(b + 16)
long l2 = l + 20;
if (is_instance_of(b,...
2016 Jun 24
6
RFC: Strong GC References in LLVM
This is a proposal to add strong GC reference types to LLVM.
We have some local (downstream) patches that are needed to prevent
LLVM's optimizer from making transforms that are problematic in the
presence of a precise relocating GC. Adding a notion of a strong GC
reference to LLVM will let us upstream these patches in a principled
manner, and will act as a measure to avoid new problematic