Lines Matching refs:plain

33 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
39 preferable to data_race(), which in turn is usually preferable to plain
44 KCSAN will complain about many types of data races involving plain
54 data_race() and even plain C-language accesses is preferable to
85 concurrently with updates to x.  Then using plain C-language writes
95 In theory, plain C-language loads can also be used for this use case.
119 In theory, plain C-language loads can also be used for this use case.
140 In theory, plain C-language loads can also be used for this use case.
166 Here are some example situations where plain C-language accesses should
190 	by default, refraining from flagging plain C-language stores:
203 Note that it is important to use plain C-language accesses in these cases,
213 However, it is even more important to comment plain C-language accesses
281 should) be plain C-language accesses.  One benefit of making them be
282 plain C-language accesses is that KCSAN can detect any erroneous lockless
467 flag any concurrent plain C-language reads from foo, and given
468 CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC=n, also any concurrent plain
509 The initialize_foo() uses a plain C-language write to foo because there