search for: postptrmap

...ot() intrinsic as it's information content > would be redundant. > > > thoughts, comments ??? > > > -Peter Lawrence. It is helpful to think of the stack/register map generation in two phases: before and after identifying the location of heap pointers. Say PrePtrMap and PostPtrMap. We don't need to know stack offsets and register names at that point, but do we need a 1-1 mapping from pointer values to identifiable physical locations. I deliberately avoid calling these values roots here, because we may have multiple live pointers derived from an object and multiple copies...

Talin, how about having the front-end generate an llvm.safe.point () intrinsic call at the desired safe points, and having the addresses of the GC roots (at that point, can vary from call to call) be the parameters (with noescape attribute) to the intrinsic, IIUC currently the GC roots are tagged, and all analysis and transform optimizations have to special case these tagged