Skip to content
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

Swift: Update SSA to reference the new use-use predicates. #19177

Merged
merged 3 commits into from
Apr 3, 2025

Conversation

aschackmull
Copy link
Contributor

Something about the use-use steps in data flow looks buggy, but I'm not going to fix that here. This is just aiming for a one-for-one semantically equivalent switch to the new use-use predicates.

@aschackmull aschackmull added the no-change-note-required This PR does not need a change note label Apr 1, 2025
@Copilot Copilot bot review requested due to automatic review settings April 1, 2025 08:06
@aschackmull aschackmull requested a review from a team as a code owner April 1, 2025 08:06
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.

Files not reviewed (2)
  • swift/ql/lib/codeql/swift/dataflow/Ssa.qll: Language not supported
  • swift/ql/lib/codeql/swift/dataflow/internal/DataFlowPrivate.qll: Language not supported

Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more

@github-actions github-actions bot added the Swift label Apr 1, 2025
@aschackmull
Copy link
Contributor Author

It appears that the changes do improve flow slightly - enough to fix a missing flow in a test.

@geoffw0
Copy link
Contributor

geoffw0 commented Apr 1, 2025

DCA is showing two new results (👍) but a slowdown in analysis times, including one project apparently timing out during analysis.

@aschackmull
Copy link
Contributor Author

DCA is showing two new results

I don't see this? (neither in the first nor second dca run)

but a slowdown in analysis times, including one project apparently timing out during analysis.

Did you look at the second dca run? I fixed an accidental CP and reran dca, so there shouldn't be any timeouts.

@aschackmull
Copy link
Contributor Author

I also cannot reproduce any of the supposed timing regressions in the second dca run locally, so I'm leaning towards considering those numbers noise.

Copy link
Contributor

@paldepind paldepind left a comment

Choose a reason for hiding this comment

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

Looks good to me. Regarding the DCA slowdown, 1/3 of the projects got faster and the remaining 2/3 got slower. So I agree that it is very likely just noise.

@aschackmull aschackmull merged commit e04075b into github:main Apr 3, 2025
19 checks passed
@aschackmull aschackmull deleted the swift/ssa-useuse branch April 3, 2025 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-change-note-required This PR does not need a change note Swift
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants