search for: tagless

...write barrier checks to see if the > object being mutated has been traced; If it hasn't, then it records > the values of all pointers contained in the object into a buffer - > for which you need the location of the pointers. Okay. If you're implementing this algorithm with a tagless collector, we may need to extend the intrinsics. >> In concurrent collectors—by which I mean those that run >> asynchronously of the mutator—write barriers may be used to mark >> the written object pointer. Even byte arrays as you describe >> require an object heade...

...linux original file, it won't change at all. Here is the link: http://www.easy-share.com/1909277789/bandstand.zip > > Another possibility could be different line endings in some > metadata file (ie '\r\n' on windows and '\n' on Linux). > The produced files are tagless. So I don't know about this... but it is a good guess -- Djeizon Barros <djzn.br at gmail.com>

...ks to see if the >> object being mutated has been traced; If it hasn't, then it records >> the values of all pointers contained in the object into a buffer - >> for which you need the location of the pointers. > > Okay. If you're implementing this algorithm with a tagless collector, > we may need to extend the intrinsics. More accurately, what I am trying to do is not only create a collector, but also create a framework for implementing different collector algorithms. I don't intend to be the person that creates the best/fastest collector, I just want to...

Gordon Henriksen wrote: > Can you be more specific the algorithm for which you need type > metadata in a write barrier? No algorithms I am aware of perform any > tracing from a write barrier. > This one does: http://citeseer.ist.psu.edu/cache/papers/cs2/442/http:zSzzSzwww.cs.technion.ac.ilzSz~erezzSzPaperszSzms-sliding-views.pdf/an-on-the-fly.pdf > Write barriers are

Djeizon Barros wrote: > > Another possibility could be different line endings in some > > metadata file (ie '\r\n' on windows and '\n' on Linux). > > > > The produced files are tagless. So I don't know about this... but > it is a good guess Its a good guess and its wrong :-). > I have uploaded a small file example for you to check. > I am curious about what is exactly producing this mismatch filesize! > I know it's ridiculous and probably too paranoid, but k...

...of its type, much the way address spaces already work? Recall again Rust's approach here, where the behavior of address space information through transforms is exactly what is relied upon. It's easy to imagine a GC root flag on pointer types, but one still needs to attach metadata to enable tagless GC as supported by the existing infrastructure. Rust simply encodes this information into the address space number; a similar approach could be envisioned with a 'GC type ID' number that could be used by the GC metadata printer to look up detailed information in e.g. module-level metadata,...

...aces already work? Recall again Rust's approach >> here, where the behavior of address space information through >> transforms is exactly what is relied upon. >> It's easy to imagine a GC root flag on pointer types, but one still >> needs to attach metadata to enable tagless GC as supported by the >> existing infrastructure. Rust simply encodes this information into the >> address space number; a similar approach could be envisioned with a >> 'GC type ID' number that could be used by the GC metadata printer to >> look up detailed informa...

On Sun, Dec 30, 2012 at 2:17 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 30 Dec 2012, at 01:54, Talin wrote: > > > I completely agree with your point about wanting to be able to attach GC > metadata to a type (rather than attaching it to a value, as is done now). > In the past, there have been two objections to this approach: first, the > overhead

On 30 Dec 2012, at 01:54, Talin wrote: > I completely agree with your point about wanting to be able to attach GC metadata to a type (rather than attaching it to a value, as is done now). In the past, there have been two objections to this approach: first, the overhead that would be added to the Pointer type - the vast majority of LLVM users don't want to have to pay an extra 4-8 bytes per

...e way address spaces already work? Recall again Rust's approach > here, where the behavior of address space information through > transforms is exactly what is relied upon. > It's easy to imagine a GC root flag on pointer types, but one still > needs to attach metadata to enable tagless GC as supported by the > existing infrastructure. Rust simply encodes this information into the > address space number; a similar approach could be envisioned with a > 'GC type ID' number that could be used by the GC metadata printer to > look up detailed information in e.g. mod...

...You don't want to write these constants by hand. :) It would also be possible to tag roots with a trace function with a prototype like "void(Object*, void (*)(Class*, Object*))" which invokes the callback for each reference in the parameter object. This is the "model 2" tagless object model, where neither tag bits nor a vtable pointer are present in all objects. Each call @llvm.gcroot must specify the metadata pointer so the collector knows how to trace the object (or find the vtable, where applicable). This is somewhat conservative with respect to certain GC behavi...

On Apr 21, 2008, at 6:23 PM, Gordon Henriksen wrote: > On Apr 21, 2008, at 20:09, Terence Parr wrote: > >> Ok, I *might* be getting this from the assembly code. ... From >> that, it will push/pop in functions? If so, that's easy enough. :) > > Yup! Sounds like you've got it. Yup, what i was missing and what somebody should add to the doc is that

...de: Update wcstok declarations. tzres: Add Aleutian Time Zone. wintrust: Set last error in WinVerifyTrust. Dirk Niggemann (1): toolhelp: Return correct handle, address, flag and lock values in LocalNext() for moveable blocks. Dmitry Timoshkov (8): widl: Generate name for a tagless union. widl: If a variable doesn't have a name provide an autogenerated one. activeds.tlb: Add typelib. ole32: Correct MkParseDisplayName spec entry. activeds: Implement ReallocADsMem. activeds: Implement AllocADsStr and FreeADsStr. user32/tests: Add some tes...