Skip to content

Tracking Issue for f16b #160630

Description

@davidtwco

This is a tracking issue for the RFC "bf16 type" (rust-lang/rfcs#3983). The feature gate for the issue is #![feature(f16b)].

Approved by the language team for experimentation in the 2026/08/06 triage meeting.

This feature is part of the "bf16" project goal from 2026 (pending in rust-lang/goals#723). It was discussed by the language team in the 2026/08/06 design meeting. It is currently being worked on by @Jamesbarford.

About tracking issues

Tracking issues are used to record the overall progress of implementation.

They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Discussion comments will get marked as off-topic or deleted. Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

Unresolved Questions

  • What to do about the ABI on targets without a defined f16b calling convention?

Implementation history

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-experimentalBlocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize).C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-f16b`#![feature(f16b)]`S-tracking-unimplementedStatus: The feature has not been implemented.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-langRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.

    Projects

    Status
    Tracking

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions