[PATCH 06/46] s390: Document operand ordering rules for .insn directive

← All discussions

Project / Subsystem

binutils / s390

Date

2026-10-05

Proposer

Jens Remus <jremus@linux.ibm.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

• Improves user understanding of the `.insn` directive.
• Standardizes operand entry, potentially simplifying parser logic.

View thread →

All attributes

project: binutils
subsystem: s390
patch_id: —
discussion_id: 20261005153947.363053-54-jremus@linux.ibm.com
source_type: public_inbox
title: [PATCH 06/46] s390: Document operand ordering rules for .insn directive
headline: s390: Document operand ordering rules for .insn directive
tldr: Documents operand ordering rules for the .insn directive in the s390 assembler.
proposer: Jens Remus <jremus@linux.ibm.com>
consensus: Proposed
outcome: proposed
sentiment_score: —
technical_tradeoffs: • Improves user understanding of the `.insn` directive.
• Standardizes operand entry, potentially simplifying parser logic.
series_id: binutils:s390: document operand ordering rules for .insn directive
series_role: reply
series_parts: []
tags: • s390
• assembler
• documentation
• instruction-format
url: https://inbox.sourceware.org/binutils/20261005153947.363053-54-jremus@linux.ibm.com
bugzilla_url: —
date: 2026-10-05T00:00:00.000Z

[PATCH 06/46] s390: Document operand ordering rules for .insn directive

This patch documents the operand ordering rules for the .insn directive in the s390 assembler. Operands should generally follow the ascending order of their field indices as specified in the Principles of Operation manuals, with exceptions noted. Composite operands are treated as single units for indexing. This documentation improves clarity and usability of the .insn directive.