[Typed throws] Workaround for LLVM miscompile of unused swifterror, add executable test #69043
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.
While experimenting with typed throws, I discovered that on x86_64 and -Onone only, the IR that typed throws generates (which is identical to IR on arm64!) ends up getting lowered in a wrong way and the execution of the program ends up taking the wrong branch, this is demonstrated by the testcase added in this PR -- the "this cannot happen" call actually happens. I don't have the ability to diagnose the LLVM problem further, and so instead this PR adds a workaround to enable executable testing of typed throws. This PR also adds a simple executable test.