@@ -6058,9 +6058,9 @@ and often @acronym{CRAN} submissions attempt to use @file{endian.h}.
60586058The latter is a @code{glibc} extension: some OSes have
60596059@file{machine/endian.h} or @file{sys/endian.h} but some have neither.
60606060@c macOS has machine/endian.h. Solaris had none.
6061- Header @file{execinfo.h} is only available on a few OSes: formwrly nor
6062- in MacOS nor Solaris, and currently not on Linux systems (such as Aloine
6063- Linux)using @code{musl}. Nor is header @file{fpu_control.h} avaialble
6061+ Header @file{execinfo.h} is only available on a few OSes: formerly nor
6062+ in MacOS nor Solaris, and currently not on Linux systems (such as Alpine
6063+ Linux) using @code{musl}. Nor is header @file{fpu_control.h} available
60646064on macOS nor @code{musl}.
60656065
60666066@item
@@ -9939,9 +9939,9 @@ of reports have been of `heap-use-after-free' errors in the X11
99399939libraries called from Tcl/Tk.
99409940
99419941Apple provide a version of the address sanitizer in recent versions of
9942- its C/C++ compiler. This will proably give messages about
9943- `malloc: nano zone abandoned' which are innocuous and can be suppressed
9944- by setting environmant variable @env{MallocNanoZone} to @code{0}.
9942+ its C/C++ compiler. This will probably give messages about
9943+ @I{ `malloc: nano zone abandoned'} which are innocuous and can be suppressed
9944+ by setting environment variable @env{MallocNanoZone} to @code{0}.
99459945@c https://stackoverflow.com/questions/64126942/malloc-nano-zone-abandoned-due-to-inability-to-preallocate-reserved-vm-space
99469946
99479947@c 1-item menu: kept to avoid spurious warning from makeinfo 6.8/7.0
@@ -9964,7 +9964,7 @@ variable
99649964ASAN_OPTIONS='detect_leaks=1'
99659965@end example
99669966@noindent
9967- However, this was made the default as from LLVM @command{clang} 3.5 and
9967+ However, this was made the default as from @I{ LLVM} @command{clang} 3.5 and
99689968@command{gcc} 5.1.0.
99699969
99709970When @abbr{LSan} is enabled, leaks give the process a failure error status (by
@@ -10123,8 +10123,8 @@ For more details on the topic see
1012310123It may or may not be possible to build @R{} itself with
1012410124@option{-fsanitize=undefined}: problems have in the past been seen with
1012510125@abbr{OpenMP}-using code with @command{gcc} but there has been success
10126- with LLVM @command{clang} up to version 16.. However, problems have been
10127- seen with LLVM @command{clang} 17 and later, including missing entry points
10126+ with @I{ LLVM} @command{clang} up to version 16.. However, problems have been
10127+ seen with @I{ LLVM} @command{clang} 17 and later, including missing entry points
1012810128and @R{} builds hanging. What has succeeded is to use @abbr{UBSAN} just for
1012910129the package under test (and not in combination with @abbr{ASAN}). To do so,
1013010130check with an unaltered @R{}, using a custom @file{Makevars} file
@@ -10153,7 +10153,6 @@ the paths used, have changed several times recently.
1015310153Apple provides a version of the undefined behaviour sanitizer in recent
1015410154versions of its C/C++ compiler. @R{} was built with Apple
1015510155@command{clang} 16 with @file{config.site} containing
10156- @noindent
1015710156@example
1015810157CC="clang -fsanitize=address,undefined"
1015910158CXX="clang++ -fsanitize=address,undefined"
@@ -10164,7 +10163,7 @@ and passed its checks.
1016410163@node Other analyses with `clang'
1016510164@subsection Other analyses with `clang'
1016610165
10167- Recent versions of LLVM @command{clang} on Linux have
10166+ Recent versions of @I{ LLVM} @command{clang} on Linux have
1016810167`@I{ThreadSanitizer}'
1016910168(@uref{https://github.com/google/sanitizers/wiki#threadsanitizer}), a
1017010169`data race detector for C/C++ programs', and `@I{MemorySanitizer}'
0 commit comments