Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BoundsSafety][doc] Fix formatting #126245

Merged
merged 2 commits into from
Feb 7, 2025
Merged

[BoundsSafety][doc] Fix formatting #126245

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
666c1d1
[BoundsSafety][doc] Add a missing newline in C snippet
pfusik Feb 7, 2025
6696886
[BoundsSafety][doc] Add a missing quote
pfusik Feb 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions clang/docs/BoundsSafety.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -959,7 +959,8 @@ that has the define.
#if defined(__has_feature) && __has_feature(bounds_safety)
#define __counted_by(T) __attribute__((__counted_by__(T)))
// ... other bounds annotations
#else #define __counted_by(T) // defined as nothing
#else
#define __counted_by(T) // defined as nothing
// ... other bounds annotations
#endif

Expand Down Expand Up @@ -987,7 +988,7 @@ and it does not guarantee other types of memory safety properties. Consequently,
it may not prevent some of the secondary bounds safety violations caused by
other types of safety violations such as type confusion. For instance,
``-fbounds-safety`` does not perform type-safety checks on conversions between
`__single`` pointers of different pointee types (e.g., ``char *__single`` →
``__single`` pointers of different pointee types (e.g., ``char *__single`` →
``void *__single`` → ``int *__single``) beyond what the foundation languages
(C/C++) already offer.

Expand All @@ -1003,4 +1004,4 @@ Try it out

Your feedback on the programming model is valuable. You may want to follow the
instruction in :doc:`BoundsSafetyAdoptionGuide` to play with ``-fbounds-safety``
and please send your feedback to `Yeoul Na <mailto:[email protected]>`_.
and please send your feedback to `Yeoul Na <mailto:[email protected]>`_.