On Sun, 21 Mar 2021 00:24:46 +0900, Akira Yokosawa wrote:
> Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
> ---
> debugging/debugging.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debugging/debugging.tex b/debugging/debugging.tex
> index fd52d9e7..3f697f58 100644
> --- a/debugging/debugging.tex
> +++ b/debugging/debugging.tex
> @@ -755,7 +755,7 @@ access to data.
> The Kernel Concurrency Sanitizer (KCSAN)~\cite{JonathanCorbet2019KCSAN}
> uses existing markings such as \co{READ_ONCE()} and \co{WRITE_ONCE()}
> to determine which concurrent accesses deserve warning messages.
> -KCSAN has a significant false-positive rate, especially in from the
> +KCSAN has a significant false-positive rate, especially from the
> viewpoint of developers thinking in terms of C as assembly language
> with additional syntax.
> KCSAN therefore provides a \co{data_race()} construct to forgive
>
Paul,
I caught this one while searching the usage of "data race" in perfbook.
I thought "data race" also deserves an entry in Glossaries, especially
because our use of "data race" is heavily related to compiler
optimizations and somewhat stricter than the common definition
found on the web.
The first of data race in Section 4.2.2 (just before QQ4.8) does
not (explicitly) talk about optimizations.
Would it be possible for you to come up with some concise definition
of data race which will fit as an entry in the Glossaries?
Thanks, Akira
