Lines Matching refs:barriers

43   barriers.  If you collector does not require such barriers, you can skip 
147 safepoint, and emitting load and store barriers.  You can also extend LLVM - 
165 * Write barriers when storing object references to the heap.  These are commonly
168 * Emission of read barriers when loading object references.  These are useful
320 barriers* and *write barriers*, respectively.  The amount of code that needs to
363 For write barriers, LLVM provides the ``llvm.gcwrite`` intrinsic function.  It
368 Many important algorithms require write barriers, including generational and
369 concurrent collectors.  Additionally, write barriers could be used to implement
379 For read barriers, LLVM provides the ``llvm.gcread`` intrinsic function.  It has
384 Read barriers are needed by fewer algorithms than write barriers, and may have a
513 This GC strategy does not support read or write barriers.  As a result, these 
580    load and store barriers.  Note that since many collectors don't require 
581    barriers at all, LLVM defaults to lowering such barriers to normal loads 
765   is compacting), but bring the added complexity of requiring write barriers.
780   marking algorithms are necessary.  Read barriers may be necessary.
852 For GCs which use barriers or unusual treatment of stack roots, the