-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add allocation information to undefined behaviour errors. #76881
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
r? @oli-obk |
cc @rust-lang/wg-diagnostics |
56a2a1a
to
25883aa
Compare
@bors r+ |
📌 Commit 25883aa has been approved by |
Add allocation information to undefined behaviour errors. So far I'm looking on information on whether the error messages are suitable. Fixes rust-lang#53325.
Add allocation information to undefined behaviour errors. So far I'm looking on information on whether the error messages are suitable. Fixes rust-lang#53325.
Add allocation information to undefined behaviour errors. So far I'm looking on information on whether the error messages are suitable. Fixes rust-lang#53325.
Interesting... All the tests passed locally (I ran |
Ahh... Hitting platform-specific errors already. It appears 32-bit platforms have different size allocations and aligns, I'll need to normalize this somehow. |
☔ The latest upstream changes (presumably #74949) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@hameerabbasi any updates on this? |
38f3c3b
to
49705e0
Compare
Since this particular error is too dependent on the target's ABI, I decided to limit the problematic tests to |
@bors r+ |
📌 Commit 49705e0 has been approved by |
⌛ Testing commit 49705e0 with merge d95895350760c80709aca44c2887b0922df1d664... |
The run failed to start AFAICT. Not my fault this time. 😆 |
@bors retry |
⌛ Testing commit 49705e0 with merge 5e453bd530c15e42696bec59d1352c15897763c5... |
Looks like something else borked the macOS runners. Should we perhaps wait until that's resolved? |
💔 Test failed - checks-actions |
@bors delegate+ r=me in a few hours |
✌️ @hameerabbasi can now approve this pull request |
@bors retry |
☀️ Test successful - checks-actions |
So far I'm looking on information on whether the error messages are suitable.
Fixes #53325.