Skip to content
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

Normalize target-triple so that llvm can recognize target os correctly #5354

Merged
merged 1 commit into from
Mar 15, 2013

Conversation

ILyoan
Copy link
Contributor

@ILyoan ILyoan commented Mar 13, 2013

LLVM could not recognize target-os when target-triple was given as like 'arm-linux-androideabi'.
Normalizing target-triple fill the missing elements.
In the case of 'arm-linux-androideabi', nomalized target-triple will be "arm-unknown-linux-androideabi" and this let llvm recognize the triple correctly. (arch: arm, vendor: unknown, os: linux, environment: android)

@ILyoan
Copy link
Contributor Author

ILyoan commented Mar 15, 2013

Rebased again. r?

bors added a commit that referenced this pull request Mar 15, 2013
LLVM could not recognize target-os when target-triple was given as like 'arm-linux-androideabi'.
Normalizing target-triple fill the missing elements. 
In the case of 'arm-linux-androideabi', nomalized target-triple will be "arm-unknown-linux-androideabi" and this let llvm recognize the triple correctly. (arch: arm, vendor: unknown, os: linux, environment: android)
@bors bors closed this Mar 15, 2013
@bors bors merged commit 10df2ea into rust-lang:incoming Mar 15, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Dec 6, 2020
Added known problem to comparison_chain docs

changelog: Added documentation to comparison_chain that explains a possible performance penalty, according to issue rust-lang#5354

This is my first PR, I hope everything has been done correctly.

Fixes rust-lang#5354
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants