Skip to content

Tracking issue for release notes of #111137: Tracking Issue for AVX512 intrinsics #141629

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

Open
rustbot opened this issue May 27, 2025 · 3 comments
Labels
F-stdarch_x86_avx512 `#![feature(stdarch_x86_avx512)]` O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) release-blog-post Marks issues tracking what text to put in the release blog post. relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@rustbot
Copy link
Collaborator

rustbot commented May 27, 2025

This issue tracks the release notes text for #111137.

cc @Amanieu -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

  • Does this need an additional compat notes section?
  • Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
# Stabilized APIs
- [AVX512 intrinsics](https://github.com/rust-lang/rust/issues/111137)

Tip

Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

Note

If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.

@rustbot rustbot added O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. relnotes Marks issues that should be documented in the release notes of the next release. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) relnotes-tracking-issue Marks issues tracking what text to put in release notes. F-stdarch_x86_avx512 `#![feature(stdarch_x86_avx512)]` needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels May 27, 2025
@saethlin saethlin removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label May 27, 2025
@sayantn
Copy link
Contributor

sayantn commented Jun 2, 2025

@rustbot label release-blog-post

This is a important step for SIMD support in Rust. The relnotes section should also include

@rustbot
Copy link
Collaborator Author

rustbot commented Jun 2, 2025

Error: Label release-blog-post can only be set by Rust team members

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #t-infra on Zulip.

@sayantn
Copy link
Contributor

sayantn commented Jun 2, 2025

🤦🏽 @Amanieu guess you have to add the label

@Amanieu Amanieu added the release-blog-post Marks issues tracking what text to put in the release blog post. label Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-stdarch_x86_avx512 `#![feature(stdarch_x86_avx512)]` O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) release-blog-post Marks issues tracking what text to put in the release blog post. relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants