[BoundsSafety] Bring full support for -fbounds-safety #9679
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci test |
|
@swift-ci llvm test |
rapidsna
requested review from
fhahn,
DougGregor,
adrian-prantl,
devincoughlin,
hnrklssn,
patrykstefanski,
apple-fcloutier and
danliew-apple
|
@swift-ci test |
|
@swift-ci llvm test |
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
from
6ad5c0c to
0066b9a
Compare
|
@swift-ci test |
|
@swift-ci llvm test |
|
@swift-ci test |
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
from
0066b9a to
5f998b8
Compare
|
@swift-ci test |
|
@swift-ci test llvm |
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
from
7d29e29 to
bdb1166
Compare
delcypher
added
the
clang:bounds-safety
devincoughlin
approved these changes
Dec 7, 2024
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
from
260d5e5 to
a4d868b
Compare
|
@swift-ci test |
|
@swift-ci test llvm |
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
2 times, most recently
from
607cee7 to
0920fa1
Compare
|
@swift-ci test |
rapidsna
force-pushed
the
dev/yeoulna/upstream-bounds-safety-swift/next
branch
from
0920fa1 to
4554416
Compare
|
@swift-ci test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-fbounds-safety is a C extension to enforce bounds safety to prevent out-of-bounds (OOB) memory accesses. The extension offers bounds annotations that programmers can use to attach bounds to pointers. Using this bounds information, the compiler inserts bounds checks on every pointer dereference, ensuring that the program does not access memory outside the specified bounds. The compiler requires programmers to provide enough bounds information so that the accesses can be checked at either run time or compile time — and it rejects code if it cannot.
For more details, please refer to
RFC discussions: https://discourse.llvm.org/t/rfc-enforcing-bounds-safety-in-c-fbounds-safety/70854
The design documentation: https://clang.llvm.org/docs/BoundsSafety.html
The bounds annotations provided by -fbounds-safety could potentially be useful to implement safe interoperation between C/C++ and safe languages such as Swift. Similar to lifetime dependency annotations as pitched here.
This patch contains collaborative work from @rapidsna @apple-fcloutier @patrykstefanski @delcypher @hnrklssn and from many other collaborators from the optimization and debugger side of support.
Cherry-picking #9665