search for: gc_root

Displaying 8 results from an estimated 8 matches for "gc_root".

2010 Oct 23
2
[LLVMdev] Cast failure in SelectionDAGBuilder
...he function being processed (according to I.Parent.Parent->dump()): define internal %tart.core.Object* @"tart.core.Object.coerce[int32](int32)->tart.core.Object"(i32 %value) gc "tart-gc" { prologue: call void @llvm.dbg.declare(metadata !{i32 %value}, metadata !48487) %gc_root = alloca %"tart.core.ValueRef[char]"*, !dbg !48488 store %"tart.core.ValueRef[char]"* null, %"tart.core.ValueRef[char]"** %gc_root %0 = bitcast %"tart.core.ValueRef[char]"** %gc_root to i8**, !dbg !48488 call void @llvm.gcroot(i8** %0, i8* null), !dbg !...
2010 Sep 25
2
[LLVMdev] Strange exception in SelectionDAGBuilder
...fails because the node type is DYNAMIC_STACKALLOC, while this code is expecting the node type to be "FrameIndex" or "TargetFrameIndex". (I don't know what either of these mean, I'm just telling you what the debugger is telling me.) Here's what the IR looks like: %gc_root = alloca %tart.collections.KeyError*, align 8, !dbg !55084 store %tart.collections.KeyError* %7, %tart.collections.KeyError** %gc_root, align 8, !dbg !55084 %9 = bitcast %tart.collections.KeyError** %gc_root to i8**, !dbg !55084 call void @llvm.gcroot(i8** %9, i8* null), !dbg !55084 As you c...
2010 Sep 26
0
[LLVMdev] Strange exception in SelectionDAGBuilder
...is DYNAMIC_STACKALLOC, while this code is expecting the node type > to be "FrameIndex" or "TargetFrameIndex". (I don't know what either of these > mean, I'm just telling you what the debugger is telling me.) > > Here's what the IR looks like: > > %gc_root = alloca %tart.collections.KeyError*, align 8, !dbg !55084 > store %tart.collections.KeyError* %7, %tart.collections.KeyError** > %gc_root, align 8, !dbg !55084 > %9 = bitcast %tart.collections.KeyError** %gc_root to i8**, !dbg !55084 > call void @llvm.gcroot(i8** %9, i8* null), !...
2013 Nov 11
0
[LLVMdev] Improving GC intrinsics in LLVM
...integer constant that is used to determine what kind of annotation this is. The 'metadata' argument is a const void* pointer, similar to the existing llvm.gcroot() argument, which can point to any constant data structure. There would be a fixed set of annotation ids, one of which would be GC_ROOT. Other kinds of type annotations could be introduced later for other purposes. AnnnotatedType instances would be folded/uniqued just like all other derived types. LLVM optimizers and code generators would need to be modified to unwrap the base type whenever an annotated type was encountered. Idea...
2012 Nov 16
3
[LLVMdev] Making VMKit2
...esktop/vmkit2/lib/j3/ClassLib' make[4]: Entering directory `/home/ela/Desktop/vmkit2/lib/j3/ClassLib/OpenJDK' llvm[4]: Compiling ClasspathReflect.ll to ClasspathReflect.bc for Release+Asserts build (bytecode) Method _ZN2j3L12getAttrBytesEPNS_8AttributEPNS_5ClassE has static linkage but uses gc_root. Functions using gc_root should not have static linkage. 0  opt             0x08eb8dc8 1  opt             0x08eb9344 2                  0x40020400 __kernel_sigreturn + 0 3                  0x40020416 __kernel_vsyscall + 2 4  libc.so.6       0x401b4c8f gsignal + 79 5  libc.so.6       0x401b82b5 abor...
2012 Nov 19
0
[LLVMdev] Making VMKit2
...gt;make[4]: Entering directory `/home/ela/Desktop/vmkit2/lib/j3/ClassLib/OpenJDK' >>>>llvm[4]: Compiling ClasspathReflect.ll to ClasspathReflect.bc for Release+Asserts build (bytecode) >>>>Method _ZN2j3L12getAttrBytesEPNS_8AttributEPNS_5ClassE has static linkage but uses gc_root. Functions using gc_root should not have static linkage. >>>>0  opt             0x08eb8dc8 >>>>1  opt             0x08eb9344 >>>>2                  0x40020400 __kernel_sigreturn + 0 >>>>3                  0x40020416 __kernel_vsyscall + 2 >>>&...
2010 Nov 08
0
[LLVMdev] Next round of DWARF issues/questions
On Nov 6, 2010, at 7:35 PM, Talin wrote: > After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters. > > However, I'm also seeing a lot of new problems which
2010 Nov 07
3
[LLVMdev] Next round of DWARF issues/questions
After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters. However, I'm also seeing a lot of new problems which weren't exposed before. After spending the better part of two