On Tue, Feb 15 2022, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote:
[...] >>> Index: clang-local.1 >>> =================================================================== >>> RCS file: /home/cvs/src/share/man/man1/clang-local.1,v >>> retrieving revision 1.22 >>> diff -u -p -p -u -r1.22 clang-local.1 >>> --- clang-local.1 7 Sep 2021 17:39:49 -0000 1.22 >>> +++ clang-local.1 5 Feb 2022 17:11:48 -0000 >>> @@ -93,6 +93,13 @@ option to treat signed integer overflows >>> prevent dangerous optimizations which could remove security critical >>> overflow >>> checks. >>> .It >>> +Only ubsan_minimal support is shipped by the base system. >>> +To make use of it, pass >>> +.Nm clang >>> +the following options: >>> +.Fl fsanitize=undefined >>> +.Fl fsanitize-minimal-runtime . > > I'm not 100% happy with this wording, I'll try to rework it. Maybe something like this? The idea is to point people to ubsan_minimal instead of assuming that ubsan isn't supported at all. I can't see a better place to document this. For more context: UBSan is supposed to catch undefined behavior at runtime and to react by printing an error message and/or aborting, etc. https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html Greg, still ok with this version? Thoughts? Index: clang-local.1 =================================================================== RCS file: /home/cvs/src/share/man/man1/clang-local.1,v retrieving revision 1.22 diff -u -p -p -u -r1.22 clang-local.1 --- clang-local.1 7 Sep 2021 17:39:49 -0000 1.22 +++ clang-local.1 16 Feb 2022 22:37:05 -0000 @@ -93,6 +93,12 @@ option to treat signed integer overflows prevent dangerous optimizations which could remove security critical overflow checks. .It +The base system ships support for the ubsan_minimal sanitizer runtime +but not for the default ubsan runtime. +See the documentation for the +.Fl fsanitize-minimal-runtime +flag. +.It The .Xr malloc 3 , .Xr calloc 3 , -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
