Lines Matching full:accesses
100 accesses via locking. E.g. the POSIX threads library, the Qt library
180 Which source code statements generate which memory accesses depends on
272 conflicting memory accesses are ordered by synchronization
288 many conflicting memory accesses in such applications and although such
295 algorithm is to verify whether all shared memory accesses follow a consistent
297 whether all interthread memory accesses are ordered by synchronization
584 There are always at least two memory accesses involved in a data
585 race. Memory accesses involved in a data race are called
586 <span class="emphasis"><em>conflicting memory accesses</em></span>. DRD prints a
664 A conflicting access involves at least two memory accesses. For
665 one of these accesses an exact call stack is displayed, and for
666 the other accesses an approximate call stack is displayed,
668 accesses. This information can be interpreted as follows:
874 source code statements triggered the conflicting accesses, it can be
909 DRD about the order of inter-thread memory accesses implemented via
1014 DRD to ignore all memory accesses performed by the current thread.
1018 DRD to stop ignoring the memory accesses performed by the current thread.
