Skip to content

Issues: rust-lang/rust

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Linking failed with f16: undefined symbol: __floatuntihf on Ubuntu 20.04 A-linkage Area: linking into static, shared libraries and binaries C-bug Category: This is a bug. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` requires-nightly This issue requires a nightly compiler in some way. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#132614 opened Nov 4, 2024 by zhassan-aws
x86-32 "f16" ABI needs SSE, incompatible with i586 targets A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` O-x86_32 Target: x86 processors, 32 bit (like i686-*) S-waiting-on-LLVM Status: the compiler-dragon is eepy, can someone get it some tea?
#131819 opened Oct 17, 2024 by RalfJung
Add f16 formatting and parsing F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` rla-silenced Silences rust-log-analyzer postings to the PR it's added on. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-libs Relevant to the library team, which will review and decide on the PR/issue.
#127013 opened Jun 27, 2024 by tgross35 Draft
Add SIMD operations that use f16 and f128 A-SIMD Area: SIMD (Single Instruction Multiple Data) C-feature-request Category: A feature request, i.e: not implemented / a PR. E-help-wanted Call for participation: Help is requested to fix this issue. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-libs Relevant to the library team, which will review and decide on the PR/issue.
#125440 opened May 23, 2024 by tgross35
Enable f16 and f128 in assembly on platforms that support it A-inline-assembly Area: Inline assembly (`asm!(…)`) E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125398 opened May 22, 2024 by tgross35
f128 symbols on powerpc64 give inaccurate results A-ABI Area: Concerning the application binary interface (ABI) C-bug Category: This is a bug. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-libs Relevant to the library team, which will review and decide on the PR/issue.
#125109 opened May 14, 2024 by tgross35
f32::from(<untyped float>) inference with f16 and f128 F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#123831 opened Apr 11, 2024 by tgross35
Improve MSVC debug info for f16 and f128 A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` O-windows-msvc Toolchain: MSVC, Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-debugging Working group: Bad Rust debugging experiences
#121837 opened Mar 1, 2024 by tgross35
Tracking Issue for f16 and f128 float types B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#116909 opened Oct 18, 2023 by traviscross
42 of 85 tasks
ProTip! Exclude everything labeled bug with -label:bug.