search for: objecthead

...to deal with low-level objects such as addresses and pointers: private final class TraceActionImpl : TraceAction { protected def tracePointer(ptrAddr:Address[Object]) { let addr:Address[ubyte] = Memory.bitCast(ptrAddr[0]); if fromSpace.contains(addr) { let header:Address[ObjectHeader] = Memory.bitCast(addr); // A gcstate of 0 means that 'header' is the head of a statically // allocated object instance, in which case we need not do // anything since it will be traced as a static root. if (header.gcstate != 0) { if (header.gcsta...

.../include/mvm/Allocator.h:19, from /cs/student/kyleklein/vmkit/include/mvm/VirtualMachine.h:18, from gcchunk.h:13, from gcalloc.h:15, from gcalloc.cpp:10: /cs/student/kyleklein/vmkit/include/mvm/Threads/Locks.h:17:26: error: ObjectHeader.h: No such file or directory Lastly whenever I configure with the --with-llvmgcc option, regardless of which of the four collectors I use I see this: /cs/student/kyleklein/llvm-source/Makefile.rules:1042: Modules require LLVM capable compiler but none is available **** I believe this has...

...abort :) -- Self-referential vs. anonymous types. This is more of a comment than a question: in my language, String literals are implemented as anonymous types because the string data follows header struct in memory. So basically there's a named type with the format: tart.core.String = { %ObjectHeader, %tart.core.String*, int32, [0 x char] } And then for a string literal of length N there's an anonymous type: { %ObjectHeader, %tart.core.String*, int32, [N x char] } It's anonymous because it doesn't make sense to generate a new named type for each different length of string. N...

...>>>>>>>>>>>> from gcalloc.cpp:10: >>>>>>>>>>>> /cs/student/kyleklein/vmkit/include/mvm/Threads/Locks.h:17:26: >>>>>>>>>>>> error: >>>>>>>>>>>> ObjectHeader.h: No such file or directory >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Lastly whenever I configure with the --with-llvmgcc option, >>>>>>>>>>>> regardless &...