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

Implement F16C intrinsics #737

Merged
merged 8 commits into from
May 9, 2019
Merged

Implement F16C intrinsics #737

merged 8 commits into from
May 9, 2019

Conversation

gnzlbg
Copy link
Contributor

@gnzlbg gnzlbg commented Apr 23, 2019

Note: avx512f enables f16c - once rust-lang/rust#60191 is merged and available on nightly we can switch these to only requiring the f16c target-feature instead.

crates/std_detect/src/detect/arch/x86.rs Outdated Show resolved Hide resolved
crates/core_arch/src/x86/f16c.rs Outdated Show resolved Hide resolved
@gnzlbg
Copy link
Contributor Author

gnzlbg commented Apr 23, 2019

@alexcrichton since the F16C PR upstream has already been r+, I think it is better to not merge this until that lands, and then just update this PR to properly use f16c.

Centril added a commit to Centril/rust that referenced this pull request Apr 23, 2019
Add f16c target_feature

This is requires for Intel 16-bit half-precision float intrinsics: https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=fp16&expand=1769 - see companion stdsimd PR: rust-lang/stdarch#737.

LLVM, Wikipedia CPUID page, and the Intel Dev Manual all call this CPUID feature "F16C", but the Intel intrinsics guide calls this "FP16C" - this is probably a bug in the intrinsics guide which we are tracking here: rust-lang/stdarch#738

r? @alexcrichton
Centril added a commit to Centril/rust that referenced this pull request Apr 23, 2019
Add f16c target_feature

This is requires for Intel 16-bit half-precision float intrinsics: https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=fp16&expand=1769 - see companion stdsimd PR: rust-lang/stdarch#737.

LLVM, Wikipedia CPUID page, and the Intel Dev Manual all call this CPUID feature "F16C", but the Intel intrinsics guide calls this "FP16C" - this is probably a bug in the intrinsics guide which we are tracking here: rust-lang/stdarch#738

r? @alexcrichton
Centril added a commit to Centril/rust that referenced this pull request Apr 23, 2019
Add f16c target_feature

This is requires for Intel 16-bit half-precision float intrinsics: https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=fp16&expand=1769 - see companion stdsimd PR: rust-lang/stdarch#737.

LLVM, Wikipedia CPUID page, and the Intel Dev Manual all call this CPUID feature "F16C", but the Intel intrinsics guide calls this "FP16C" - this is probably a bug in the intrinsics guide which we are tracking here: rust-lang/stdarch#738

r? @alexcrichton
Centril added a commit to Centril/rust that referenced this pull request Apr 23, 2019
Add f16c target_feature

This is requires for Intel 16-bit half-precision float intrinsics: https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=fp16&expand=1769 - see companion stdsimd PR: rust-lang/stdarch#737.

LLVM, Wikipedia CPUID page, and the Intel Dev Manual all call this CPUID feature "F16C", but the Intel intrinsics guide calls this "FP16C" - this is probably a bug in the intrinsics guide which we are tracking here: rust-lang/stdarch#738

r? @alexcrichton
@gnzlbg gnzlbg closed this Apr 28, 2019
@gnzlbg gnzlbg reopened this Apr 28, 2019
@gnzlbg gnzlbg closed this May 2, 2019
@gnzlbg gnzlbg reopened this May 2, 2019
@gnzlbg gnzlbg closed this May 7, 2019
@gnzlbg gnzlbg reopened this May 7, 2019
@gnzlbg gnzlbg closed this May 8, 2019
@gnzlbg gnzlbg reopened this May 8, 2019
@gnzlbg gnzlbg merged commit e923c9e into rust-lang:master May 9, 2019
@gnzlbg
Copy link
Contributor Author

gnzlbg commented May 9, 2019

CI is green again.

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.

None yet

2 participants