-
Notifications
You must be signed in to change notification settings - Fork 100
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
[CIR][CodeGen] Use signed type for result of ptrdiff operation. #355
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this!
05ffb2a
to
34fceae
Compare
58eb780
to
a7816b1
Compare
Test fails seem unrelated, looks like current trunk is failing on Mac and Windows. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Yea, I fixed that yesterday, but a rebase is needed in order "to see it". Let me try to land this before you have to rebase. |
It worked! If you look at the commit list in github, you can see which commits landed green (there's a green check mark). |
Interesting. All our PRs started failing on Win/Mac after rebase, that's why I thought it's a trunk problem. |
It was, but you created your PR before I landed 8bd43c4 |
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
…#355) Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).
Before this fix attached test case has been failing due to type mismatch (signed vs unsigned).