Name explicit registers in conflict register errors for inline assembly#117912
Name explicit registers in conflict register errors for inline assembly#117912bors merged 1 commit intorust-lang:masterfrom
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @petrochenkov (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
|
Some more tests in |
This comment has been minimized.
This comment has been minimized.
|
r=me with the style nit addressed #117912 (comment) |
|
@bors r+ |
Name explicit registers in conflict register errors for inline assembly
Name explicit registers in conflict register errors for inline assembly
Name explicit registers in conflict register errors for inline assembly
|
💔 Test failed - checks-actions |
|
@bors retry |
|
(CI appears to be down in general.) |
|
@bors retry |
Name explicit registers in conflict register errors for inline assembly
|
💔 Test failed - checks-actions |
|
@bors retry |
Name explicit registers in conflict register errors for inline assembly
|
💔 Test failed - checks-actions |
|
@bors retry |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (4e3dc97): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.874s -> 673.421s (0.23%) |
No description provided.