Avoid deref/ref cycles for no-op coercions between unsafe pointers#26336
Merged
bors merged 1 commit intorust-lang:masterfrom Jun 18, 2015
Merged
Avoid deref/ref cycles for no-op coercions between unsafe pointers#26336bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Contributor
|
r? @nrc (rust_highfive has picked a reviewer for you, use r? to override) |
dotdash
force-pushed
the
raw_ptr_coercions
branch
from
61282c4 to
3c67921
Compare
Member
|
@bors: r+ |
Collaborator
|
📌 Commit 3c67921 has been approved by |
Collaborator
|
⌛ Testing commit 3c67921 with merge d408ed3... |
Collaborator
|
💔 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.
dotdash
force-pushed
the
raw_ptr_coercions
branch
from
3c67921 to
cabd068
Compare
Contributor
Author
Collaborator
bors
added a commit
that referenced
this pull request
Jun 16, 2015
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.
Collaborator
|
💔 Test failed - auto-mac-64-nopt-t |
Member
|
@bors: retry On Tue, Jun 16, 2015 at 6:32 AM, bors notifications@github.com wrote:
|
bors
added a commit
that referenced
this pull request
Jun 18, 2015
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.
Collaborator
Collaborator
brson
added
the
relnotes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.