-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Revert "[opt] remove trivially dead instructions in mandatory combine" #31077
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "[opt] remove trivially dead instructions in mandatory combine" #31077
Conversation
@swift-ci please test source compatibility |
Reverting this PR fixes Kingfisher project failures in debug configuration. |
/cc @zoecarver @gottesmm |
@swift-ci please smoke test |
Looks like there is an unrelated break now related to |
@xedin we tested fairly extensively (source compatibility and device filecheck preset). What's the error? |
@zoecarver https://ci.swift.org/view/Source%20Compatibility/job/swift-master-source-compat-suite-debug/2848/artifact/swift-source-compat-suite/ (Kingfisher fails in 4 configurations). |
Hmm I see. It might have somehow removed the destroy_addr. I'll play around with it a bit and see if I can make a reproducer. |
Looks like the kingfisher build is now succeeding. Still no reproducer but, it was something to do with one of the enum operators. |
@xedin I'll keep trying to debug why the crash happened but I'm beginning to suspect it wasn't this commit, actually. When building Kingfisher from master, it doesn't crash anymore but, when I checkout a5d1214220b8ddf29acf7c08c8bb42993ed56c54 and try to build I get the crash. Anyway, as I said, I'll keep trying to figure out what the cause is. |
Ignore the last comment. I tracked down the issue, it was this commit (oops). Here's the pattern that we incorrectly remove (
|
Reverts #30429
Testing to see whether this is a cause of SIL failure in source compatibility project Kingfisher.