[Test] Disable test with debug stdlibs. #67559
Merged
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.
Now that the SwiftStdlib 5.9 macro has been defined, this test failing with stdlib debug builds is exposed. That is occurring because the back deployment fallback
$ss9TaskLocalC13withValueImpl_9operation4file4lineqd__xn_qd__yYaKXESSSutYaKlFTwB
is now being called.In unoptimized stdlib builds, the version of that function that is deserialized into the test case module features an unoptimized copy of the argument
%1
into a temporary (%10
):This is a problem because
swift_task_localValuePush
allocates in the async stack (see rdar://107275872) but that fact isn't encoded in SIL (the fix for which is tracked by rdar://108260399), so thealloc_stack
/dealloc_stack
surrounding that call result in a violation of stack discipline.In optimized stdlib builds, the copy has been optimized away by the time the function is deserialized into the test case module:
The argument
%1
is forwarded into the apply ofswift_task_localValuePush
.rdar://112898559