-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Avoid deref/ref cycles for no-op coercions between unsafe pointers #26336
Conversation
r? @nrc (rust_highfive has picked a reviewer for you, use r? to override) |
61282c4
to
3c67921
Compare
@bors: r+ |
📌 Commit 3c67921 has been approved by |
⌛ Testing commit 3c67921 with merge d408ed3... |
💔 Test failed - auto-mac-64-opt |
Unlike coercing from reference to unsafe pointer, coercing between two unsafe pointers doesn't need an AutoDerefRef, because there is no region that regionck would need to know about. In unoptimized libcore, this reduces the number of "auto_deref" allocas from 174 to 4.
3c67921
to
cabd068
Compare
Unlike coercing from reference to unsafe pointer, coercing between two unsafe pointers doesn't need an AutoDerefRef, because there is no region that regionck would need to know about. In unoptimized libcore, this reduces the number of "auto_deref" allocas from 174 to 4.
💔 Test failed - auto-mac-64-nopt-t |
@bors: retry On Tue, Jun 16, 2015 at 6:32 AM, bors notifications@github.com wrote:
|
Unlike coercing from reference to unsafe pointer, coercing between two unsafe pointers doesn't need an AutoDerefRef, because there is no region that regionck would need to know about. In unoptimized libcore, this reduces the number of "auto_deref" allocas from 174 to 4.
Unlike coercing from reference to unsafe pointer, coercing between two
unsafe pointers doesn't need an AutoDerefRef, because there is no region
that regionck would need to know about.
In unoptimized libcore, this reduces the number of "auto_deref" allocas
from 174 to 4.