[BoundsSafety] Fix tests broken by change to how debug info in macros is handled #11739
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.
#11723 change changed how debug info for macros were handled.
This broke a bunch of the BoundsSafety tests because they were testing the debug info used by some macros. In particular
opt-remarkstest use debug info and the location of the<count>in__counted_by(<count>)changed to point at the macro argument instead the beginning of the macrotrap-reasonstests explicitly tested the debug location of access that happened through a macro. The debug location previously pointed at the beginning of theARRAYmacro and now it points at thearrayargument to the macro.rdar://163727761&163727775&163727819&163727893&163727903