RE: [PATCH] x86: separate AVX10.1-aux from AVX10.2
Project / Subsystem
binutils / x86
Date
2026-07-17
Proposer
"Jiang, Haochen" <haochen.jiang@intel.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Choosing `avx10.1aux` over `avx10_v1_aux` might be simpler for direct use but less aligned with potential documentation standards.
- • Ensuring naming consistency across related extensions is important for usability but may require waiting for external input (from AMD).
All attributes
- project
- binutils
- subsystem
- x86
- patch_id
- —
- discussion_id
- SJ5PPF77D28E3C21A8084B3CB97F8194B52ECC62@SJ5PPF77D28E3C2.namprd11.prod.outlook.com
- source_type
- public_inbox
- title
- RE: [PATCH] x86: separate AVX10.1-aux from AVX10.2
- headline
- x86: separate AVX10.1-aux from AVX10.2
- tldr
- Discussion on naming conventions for AVX10.1-aux and AVX10.2-aux feature bits in the assembler, seeking AMD's opinion.
- proposer
- "Jiang, Haochen" <haochen.jiang@intel.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Choosing `avx10.1aux` over `avx10_v1_aux` might be simpler for direct use but less aligned with potential documentation standards.
- • Ensuring naming consistency across related extensions is important for usability but may require waiting for external input (from AMD).
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • binutils
- • x86
- • AVX
- • CPU extensions
- • naming conventions
- bugzilla_url
- —
- date
- 2026-07-17T00:00:00.000Z
RE: [PATCH] x86: separate AVX10.1-aux from AVX10.2
This email is a follow-up to a discussion about naming conventions for new x86 instruction set extensions in the GNU assembler. The core of the discussion is the naming of AVX10.1-aux feature bits. Jiang, Haochen, references a previous exchange where Jan Beulich suggested aligning the name with documentation, potentially using avx10_v1_aux. Haochen leans towards avx10.1aux if v1 is not preferred, but notes that this is an AMD-proposed feature and they need to confirm their naming preference to ensure consistency with AVX10_V2_AUX.