Displaying 3 results from an estimated 3 matches for "lfield".
Did you mean:
field
2004 Jan 05
1
slow and max connection errors
...swashington,dwheeling,beaster,bfitch,breynoso,bwatson,cbowen,csanford,dg
oldfluss,dhuscher,dkalutkiewicz,dmauz,dmcintosh,dschneider,dtinsley,dwhe
eling,dyoung,gblack,gbonner,gfriedman,gmarciniak,imoore,jburns,jmayer,jm
ccormick,jmercer,jpallotto,jrodriguez,jsabel,jvirgil,jvoss,kjohnson,lbro
wn,lfields,lperkins,mfleming,mhaynes,mheimple,mkarge,mwager,nwallace,rbo
wen,robbowen,rrestivo,rstearns,rwinterboer,skirtland,swright,syoung,tbur
gess,tswapp,twolf,wgriffith
create mode = 750
directory mode = 2750
I think that's it. Thanks
On Jan 5, 2004, at 9:36 AM, Jason Balicki...
2016 Jul 12
2
RFC: Strong GC References in LLVM
...gt;> bitwise representation of a GC reference 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)...
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