Uh oh!
There was an error while loading. Please reload this page.
Ensure main() always has external linkage - #48541
Merged
Merged
Conversation
This ensures that the entry function is never elided due to inlining, even with `inline(always)`. Fixesrust-lang#47783. There were a couple of possible ways of addressing this issue; I simply picked the one that seemed most direct. A warning could be appropriate, but considering using inlining hints in other places it doesn't apply also throws no warnings, and it seems like an edge case anyway, I haven't added one for now.
rust-highfive
commented
Feb 25, 2018
Contributor
(rust_highfive has picked a reviewer for you, use r? to override) |
michaelwoerister
commented
Feb 26, 2018
Member
Thanks for the PR, @varkor! Seems fine to do it that way. |
michaelwoerister
commented
Feb 26, 2018
Member
@bors r+ |
bors
commented
Feb 26, 2018
Collaborator
📌 Commit 2466644 has been approved by |
kennytm added a commit
to kennytm/rust
that referenced
this pull request
Feb 27, 2018
…ster Ensure main() always has external linkage This ensures that the entry function is never elided due to inlining, even with `inline(always)`. Fixesrust-lang#47783. There were a couple of possible ways of addressing this issue; I simply picked the one that seemed most direct. A warning could be appropriate, but considering using inlining hints in other places it doesn't apply also throws no warnings, and it seems like an edge case anyway, I haven't added one for now.
alexcrichton
commented
Feb 27, 2018
Member
@bors: rollup |
kennytm added a commit
to kennytm/rust
that referenced
this pull request
Feb 28, 2018
…ster Ensure main() always has external linkage This ensures that the entry function is never elided due to inlining, even with `inline(always)`. Fixesrust-lang#47783. There were a couple of possible ways of addressing this issue; I simply picked the one that seemed most direct. A warning could be appropriate, but considering using inlining hints in other places it doesn't apply also throws no warnings, and it seems like an edge case anyway, I haven't added one for now.
bors added a commit
that referenced
this pull request
Feb 28, 2018
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
This ensures that the entry function is never elided due to inlining, even with
inline(always). Fixes#47783.There were a couple of possible ways of addressing this issue; I simply picked the one that seemed most direct. A warning could be appropriate, but considering using inlining hints in other places it doesn't apply also throws no warnings, and it seems like an edge case anyway, I haven't added one for now.