Lines Matching full:plain

18 1.	Plain C-language accesses (unmarked), for example, "a = b;"
39 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
45 preferable to data_race(), which in turn is usually preferable to plain
50 KCSAN will complain about many types of data races involving plain
60 data_race() and even plain C-language accesses is preferable to
91 concurrently with updates to x.  Then using plain C-language writes
101 In theory, plain C-language loads can also be used for this use case.
125 In theory, plain C-language loads can also be used for this use case.
146 In theory, plain C-language loads can also be used for this use case.
162 Plain C-language stores can also be used for this use case.  However,
169 Use of Plain C-Language Accesses
172 Here are some example situations where plain C-language accesses should
196 	by default, refraining from flagging plain C-language stores:
209 Note that it is important to use plain C-language accesses in these cases,
236 However, it is even more important to comment plain C-language accesses
304 should) be plain C-language accesses.  One benefit of making them be
305 plain C-language accesses is that KCSAN can detect any erroneous lockless
490 flag any concurrent plain C-language reads from foo, and given
491 CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC=n, also any concurrent plain
532 The initialize_foo() uses a plain C-language write to foo because there