Skip to content

Conversation

@delcypher
Copy link

…oundsSafety.cpp

When d061ddb was landed in our
downstream branches this was prior to the code being reviewed again in
llvm#169117 which introduced a
bunch of NFC changes.

This patch incorporates the llvm.org version of
`InstrumentationRuntimeBoundsSafety.cpp`. This will make it simpler to
consume upstream changes to this file.
…fety plugin (llvm#175082)

This change makes several improvements:

* Adds some additional logging in the
`InstrumentationBoundsSafetyStopInfo` constructor. In particular logging
is now emitted along the success path so we can see what the plugin
computed.
* `ComputeStopReasonAndSuggestedStackFrame` now logs if the debug info
vs no debug info path is taken.
* `CheckIfRuntimeIsValid` now prints the correct module path. Previously
it always printed `<unknown module>`.
* `Deactivate` now prints the breakpoint number correctly. Previously
this would try to print signed breakpoints IDs as unsigned. This problem
was observable because internal breakpoints use negative breakpoint IDs.

rdar://167797706
(cherry picked from commit 631645c)
@delcypher delcypher self-assigned this Jan 9, 2026
@delcypher delcypher requested a review from a team as a code owner January 9, 2026 20:17
@delcypher delcypher added the clang:bounds-safety Issue relating to the experimental -fbounds-safety feature in Clang label Jan 9, 2026
@delcypher
Copy link
Author

@swift-ci test

@delcypher
Copy link
Author

@swift-ci please test linux

@delcypher
Copy link
Author

@swift-ci test linux

Copy link

@JDevlieghere JDevlieghere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@JDevlieghere JDevlieghere merged commit 1032c9e into swiftlang:swift/release/6.3 Jan 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clang:bounds-safety Issue relating to the experimental -fbounds-safety feature in Clang

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants