@@ -5368,16 +5368,85 @@ The ``#pragma comment(lib, ...)`` directive is
supported on all ELF targets.
The second parameter is the library name (without the traditional Unix prefix
of
``lib``). This allows you to provide an implicit link of dependent libraries.
-Evaluating Object Size Dynamically
-==
+Evaluating Object Size
+==
+
+Clang supports the builtins ``__builtin_object_size`` and
+``__builtin_dynamic_object_size``. The semantics are compatible with GCC's
+builtins of the same names, but the details are slightly different.
+
+.. code-block:: c
+
+ size_t __builtin_[dynamic_]object_size(const void *ptr, int type)
+
+Returns the number of accessible bytes ``n`` past ``ptr``. The value returned
+depends on ``type``, which is required to be an integer constant between 0 and
+3:
+
+* If ``type & 2 == 0``, the least ``n`` is returned such that accesses to
+ ``(const char*)ptr + n`` and beyond are known to be out of bounds. This is
+ ``(size_t)-1`` if no better bound is known.
+* If ``type & 2 == 2``, the greatest ``n`` is returned such that accesses to
+ ``(const char*)ptr + i`` are known to be in bounds, for 0 <= ``i`` < ``n``.
+ This is ``(size_t)0`` if no better bound is known.
-Clang supports the builtin ``__builtin_dynamic_object_size``, the semantics are
-the same as GCC's ``__builtin_object_size`` (which Clang also supports), but
-``__builtin_dynamic_object_size`` can evaluate the object's size at runtime.
-``__builtin_dynamic_object_size`` is meant to be used as a drop-in replacement
-for ``__builtin_object_size`` in libraries that support it.
+.. code-block:: c
+
+ char small[10], large[100];
+ bool cond;
+ // Returns 100: writes of more than 100 bytes are known to be out of bounds.
+ int n100 = __builtin_object_size(cond ? small : large, 0);
+ // Returns 10: writes of 10 or fewer bytes are known to be in bounds.
+ int n10 = __builtin_object_size(cond ? small : large, 2);
+
+* If ``type & 1 == 0``, pointers are considered to be in bounds if they point
+ into the same storage as ``ptr`` -- that is, the same stack object, global
+ variable, or heap allocation.
+* If ``type & 1 == 1``, pointers are considered to be in bounds if they point
+ to the same subobject that ``ptr`` points to. If ``ptr`` points to an array
+ element, other elements of the same array, but not of enclosing arrays, are
+ considered in bounds.
+
+.. code-block:: c
+
+ struct X { char a, b, c; } x;
+ static_assert(__builtin_object_size(, 0) == 3);
+ static_assert(__builtin_object_size(, 0) == 2);
+ static_assert(__builtin_object_size(, 1) == 1);
+
+.. code-block:: c
-For instance, here is a program that ``__builtin_dynamic_object_size`` will
make
+ char a[10][10][10];
+ static_assert(__builtin_object_size(, 1) == 1000);
+ static_assert(__builtin_object_size([1], 1) == 900);
+ static_assert(__builtin_object_size([1][1], 1) == 90);
+ static_assert(__builtin_object_size([1][1][1], 1) == 9);
+
+The values returned by this builtin are a best effort conservative
approximation
+of the correct answers. When ``type & 2 == 0``, the true value is less than or
+equal to the value returned by the builtin, and when ``type & 2 == 1``, the
true
+value is greater than or equal to the value returned by the builtin.
+
+For ``__builtin_object_size``, the value is determined entirely at compile
time.
+With optimization enabled, better results will be produced, especially when the
+call to ``__builtin_object_size`` is in a different function from the formation
+of the pointer. Unlike in GCC, enabling optimization in Clang does not allow
+more information about subobjects to be determined, so the ``type & 1 == 1``
+case will often give imprecise results when used across a function call
boundary
+even when optimization is enabled.
+
+`The ``pass_object_size`` and ``pass_dynamic_object_size`` attributes
`_
allanjude wrote:
the leading ` here makes `pass_object_size` not get the right treatment
https://github.com/llvm/llvm-project/pull/96573
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
