Skip to content

[ownership] cd7c9e97e46a0141e37f10fbfb74c094e0576ff3 followups #35563

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

Conversation

gottesmm
Copy link
Contributor

Fixes stuff from #35522.

@gottesmm gottesmm requested a review from atrick January 22, 2021 22:27
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test

@gottesmm
Copy link
Contributor Author

@swift-ci test windows platform

We were using std::next on the pointer, not the iterator meaning we were
accessing bad memory.
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test

@gottesmm gottesmm merged commit 1e039cc into swiftlang:main Jan 23, 2021
@gottesmm gottesmm deleted the pr-cd7c9e97e46a0141e37f10fbfb74c094e0576ff3-followups branch January 23, 2021 03:05
Copy link
Contributor

@atrick atrick left a comment

Choose a reason for hiding this comment

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

@gottesmm thanks. I have one post-commit review comment.

auto *valInsertPt = val->getDefiningInsertionPoint();
if (!valInsertPt)
auto *nextInsertPt = val->getNextInstruction();
if (!nextInsertPt)
Copy link
Contributor

Choose a reason for hiding this comment

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

I actually don't think we should ever bailout after getNextInstruction. Can't we just assert in side getNextInstruction that it isn't called on a terminator?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants