Add linkage attribute to (non-gnu89) inline functions #116
Conversation
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
TheDan64
reviewed
Jun 20, 2019
TheDan64
reviewed
Jun 20, 2019
TheDan64
approved these changes
Jun 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change was prompted by a linker error in bzip2. Using the linkage feature and adding the
#[linkage = "external"]attribute to inlined Rust functions (translated from non-gnu89 inlined extern functions) avoids the linker issue. This due to the wayrustchandles functions with explicit linkage (see mono.rs).After additional testing, it does not seem necessary to add a
#[linkage = "internal"]attribute on static inlined functions.