Tracking Issue for AVX512 intrinsics (original) (raw)
Navigation Menu
Appearance settings
- AI CODE CREATION
* GitHub CopilotWrite better code with AI
* GitHub SparkBuild and deploy intelligent apps
* GitHub ModelsManage and compare prompts
* MCP RegistryNewIntegrate external tools - DEVELOPER WORKFLOWS
* ActionsAutomate any workflow
* CodespacesInstant dev environments
* IssuesPlan and track work
* Code ReviewManage code changes - APPLICATION SECURITY
* GitHub Advanced SecurityFind and fix vulnerabilities
* Code securitySecure your code as you build
* Secret protectionStop leaks before they start - EXPLORE
* Why GitHub
* Documentation
* Blog
* Changelog
* Marketplace
- AI CODE CREATION
- BY COMPANY SIZE
* Enterprises
* Small and medium teams
* Startups
* Nonprofits - BY USE CASE
* App Modernization
* DevSecOps
* DevOps
* CI/CD
* View all use cases - BY INDUSTRY
* Healthcare
* Financial services
* Manufacturing
* Government
* View all industries
- BY COMPANY SIZE
- EXPLORE BY TOPIC
* AI
* Software Development
* DevOps
* Security
* View all topics - EXPLORE BY TYPE
* Customer stories
* Events & webinars
* Ebooks & reports
* Business insights
* GitHub Skills - SUPPORT & SERVICES
* Documentation
* Customer support
* Community forum
* Trust center
* Partners
- EXPLORE BY TOPIC
- COMMUNITY
* GitHub SponsorsFund open source developers - PROGRAMS
* Security Lab
* Maintainer Community
* Accelerator
* Archive Program - REPOSITORIES
* Topics
* Trending
* Collections
- COMMUNITY
- Pricing
Provide feedback
We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
Notifications You must be signed in to change notification settings
Additional navigation options
Closed
[Tracking Issue](/rust-lang/rust/issues?q=type:"Tracking Issue")
1 of 3 issues completed
Closed
Tracking Issue for AVX512 intrinsics
#111137
Tracking Issue
1 of 3 issues completed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-stdarch_x86_avx512`#![feature(stdarch_x86_avx512)]`O-x86_32Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.
Milestone
Description
opened
Feature gate: #![feature(stdarch_x86_avx512)]
This is a tracking issue for the AVX-512 (and related extensions) intrinsics in core::arch.
Public API
This feature covers all of the intrinsics from the following features:
avx512bf16avx512bitalgavx512bwavx512cdavx512favx512ifmaavx512vbmiavx512vbmi2avx512vnniavx512vpopcntdqgfnivaesvpclmulqdq
VEX variants
avxifmaavxneconvertavxvnniavxvnniint16avxvnniint8
Implementation History
- Split the stdsimd feature into separate features stdarch#1486
- Implicitly enable evex512 if avx512 is enabled #121088
- Stop using the avx512er and avx512pf x86 target features #125498
- Expand avx512_target_feature to include VEX variants #126617
Steps
- Final comment period (FCP)1
- Stabilization PR
Unresolved Questions and Other Concerns
_mm512_reduce_add_ps and friends are setting fast-math flags they should not set stdarch#1533How will we handle AVX10?_mm512_shrdv_* intrinsics have incorrect argument order #130365- We need
i1xNsupport to call LLVM intrinsics foravx512vp2intersect.
Footnotes
Sub-issues
Metadata
Metadata
Assignees
No one assigned
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-stdarch_x86_avx512`#![feature(stdarch_x86_avx512)]`O-x86_32Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.
Type
[Tracking Issue](/rust-lang/rust/issues?q=type:"Tracking Issue")
Projects
No projects
Milestone
Relationships
None yet
Development
No branches or pull requests