[llvm-dev] RFC: Strong GC References in LLVM

[Lawrence, Peter via llvm-dev]

> >
> > Sounds like “volatile” to me …

> volatile accesses can't be sunk (i.e. changed to execute in a subset of the cases it would have executed in the original > > program) or elided (e.g. if the result of the load is unused), but both of these are valid for gc references.

> -- Sanjoy

Sanjoy,
             Thanks.  So it sounds "volatile"-ish, is it conceptually possible to spell out its
semantics in detail ?   if so then it might sound like a (yet another) attribute "like" volatile.

IE basically I'm agreeing with #2, and you don't need to spell it out in detail just
for my sake, I'm really asking "can it be spelled out in detail" when it comes to
documenting the IR, such that someone writing an optimization pass will be able
to do the right thing.
 
--Peter.