public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-4724] middle-end/70090: Document that -fsanitize=object-size uses dynamic size
@ 2022-12-15 17:53 Siddhesh Poyarekar
0 siblings, 0 replies; only message in thread
From: Siddhesh Poyarekar @ 2022-12-15 17:53 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:7283380a5829150cc820ab3b25c4d91cad372eec
commit r13-4724-g7283380a5829150cc820ab3b25c4d91cad372eec
Author: Siddhesh Poyarekar <siddhesh@gotplt.org>
Date: Thu Dec 15 11:29:23 2022 -0500
middle-end/70090: Document that -fsanitize=object-size uses dynamic size
Fix the documentation to say that object sizes are deduced using
__builtin_dynamic_object_size.
gcc/ChangeLog:
PR middle-end/70090
* doc/invoke.texi (-fsanitize=object-size): Use
__builtin_dynamic_object_size instead of
__builtin_object_size.
Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
Diff:
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f48df64cc2a..a50417a4ab7 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -16744,8 +16744,8 @@ or when a method or constructor is invoked on insufficiently aligned object.
@item -fsanitize=object-size
@opindex fsanitize=object-size
This option enables instrumentation of memory references using the
-@code{__builtin_object_size} function. Various out of bounds pointer
-accesses are detected.
+@code{__builtin_dynamic_object_size} function. Various out of bounds
+pointer accesses are detected.
@item -fsanitize=float-divide-by-zero
@opindex fsanitize=float-divide-by-zero
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-12-15 17:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-15 17:53 [gcc r13-4724] middle-end/70090: Document that -fsanitize=object-size uses dynamic size Siddhesh Poyarekar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).