未翻訳

このページはまだ翻訳されていません。英語の原文を表示しています。

OpenQASM 3 feature table

Below is a list of the OpenQASM 3 language features.

For more details on these capabilities, see the OpenQASM 3.X Live Specification.

Key:

• ❌ Not supported
• 🟡 Partial support
• ✅ Supported

The meaning of the complete "supported" mark depends on the column:

• Qiskit SDK: The feature can be parsed by qiskit.qasm3.loads (by using the qiskit-qasm3-import extension), represented in a QuantumCircuit, and exported to OpenQASM 3 by qiskit.qasm3.dumps.

• IBM Qiskit Runtime: A circuit containing the corresponding Qiskit feature can be successfully executed on hardware through IBM® Qiskit Runtime.

The meaning of "partial support" typically depends on the linked notes.

備考

The most common method of submitting circuits to IBM Qiskit Runtime is to create the circuit in the Python-space interface to Qiskit SDK. Circuits constructed and submitted in this manner do not need to be loaded from OpenQASM 3 files into Qiskit SDK.

If you do not use OpenQASM 3 directly yourself, you can safely use features that are supported for representation in Qiskit SDK, export to OpenQASM 3, and submission to IBM Qiskit Runtime. This includes features that cannot be loaded by Qiskit SDK from OpenQASM 3.

OpenQASM 3 Feature	Qiskit SDK feature	Qiskit SDK	IBM Qiskit Runtime	Notes
comments		✅	✅	1
QASM vstring		✅	✅	1
include		🟡	❌	1, 7
unicode names		✅	✅
qubit	Qubit and QuantumRegister	✅	🟡	2
bit	Clbit and ClassicalRegister	✅	✅	3
bool	expr.Var and classical expressions	🟡	✅	4
int		❌	✅	4
uint	expr.Var and classical expressions	🟡	✅	4
float	expr.Var and classical expressions	🟡	🟡	4
angle	Implicit, as gate parameters	❌	🟡	4
complex		❌	❌	4
const		❌	❌	4
pi/π/tau/τ/euler/ℇ	Constant-folded into gate parameters	✅	✅
Aliasing: let	Quantum and classical registers	🟡	❌	5
register concatenation	Quantum and classical registers	🟡	❌	5
casting	expr.Cast classical expressions	🟡	🟡	4
duration		❌	❌
durationof		❌	❌
ns/µs/us/ms/s/dt	Durations of delay and box	✅	✅	6
stretch	expr.Stretch	🟡	🟡	4, 6
delay	Delay/QuantumCircuit.delay	✅	✅	6
barrier	Barrier/QuantumCircuit.barrier	✅	✅
box	BoxOp/QuantumCircuit.box	✅	❌	6
Built-in U	UGate/QuantumCircuit.u	✅	✅
gate		🟡	🟡	7
gphase	QuantumCircuit.global_phase	🟡	❌	7
ctrl @/ negctrl @	AnnotatedOperation	🟡	❌	7
inv @	AnnotatedOperation	🟡	❌	7
pow(k) @	AnnotatedOperation	🟡	❌	7
reset	Reset/QuantumCircuit.reset	✅	✅
measure	Measure/QuantumCircuit.measure	✅	✅
bit operations		🟡	✅	4
boolean operations		🟡	✅	4
arithmetic expressions		🟡	🟡	4
comparisons		🟡	✅	4
if	QuantumCircuit.if_test	✅	✅	8
else	QuantumCircuit.if_test	✅	✅	8
else if	QuantumCircuit.if_test	✅	❌	8
for loops	QuantumCircuit.for_loop	🟡	❌	8
while loops	QuantumCircuit.while_loop	✅	❌	8
continue	QuantumCircuit.continue_loop	🟡	❌	8
break	QuantumCircuit.break_loop	🟡	❌	8
return		❌	❌
extern		❌	❌
def subroutines (classical)		❌	❌
def subroutines (quantum)		❌	❌
input	QuantumCircuit.add_input	✅	🟡	4, 9
output		❌	❌

Notes

1. These OpenQASM 3 program features have no impact on the execution and Qiskit strips them out as part of parsing the files. Files that use them can be submitted but they will have no effect. For include files, stdgates.inc is currently supported as input to Qiskit, and backend execution always requires circuits to have been compiled to the backend Instruction Set Architecture (ISA), where include files are irrelevant.

2. Qiskit SDK supports parsing and dumping OpenQASM 3 files with any qubit declarations. For execution on hardware, only circuits defined in terms of hardware qubits (for example, $0) are valid. Qiskit SDK automatically outputs OpenQASM 3 in terms of the supported hardware-qubit identifiers if the circuit was transpiled for a backend with layout information.

3. bit- and bit[n]-typed variable declarations in Qiskit SDK correspond to Clbit and ClassicalRegister declarations.

4. As of July 2025, Qiskit SDK can represent local variables of a restricted set of types, can represent many runtime operations on these objects, and supports outputting them to OpenQASM 3. However, Qiskit SDK (through qiskit-qasm3-import v0.6.0) does not support parsing OpenQASM 3 files that contain variable declarations, and has very limited support for parsing variable expressions. In general, most of what Qiskit can represent in its expression system can be executed on suitable dynamic circuits hardware, even if the expression cannot yet be parsed by Qiskit SDK. See the Qiskit documentation of the qiskit.circuit.classical module for the most up-to-date information.

5. Qiskit SDK can represent register aliasing for both quantum and classical registers, but it is strongly discouraged to use aliasing of classical registers. Most expressions on classical registers do not work with aliases, and aliased classical registers are not supported for execution on hardware. The Qiskit OpenQASM 3 parser can resolve let alias statements that bind the result of register concantenation.

6. Qiskit SDK supports explicit delays via QuantumCircuit.delay, and circuit boxes (QuantumCircuit.box) can also have explicit durations. These durations can include classical expressions of stretch variables. Qiskit SDK (as of July 2025 through qiskit-qasm3-import v0.6.0) does not support parsing declarations of type duration or type stretch from OpenQASM 3 files. Hardware has limited support for durations including stretch.

7. Circuits must be transpiled to the backend ISA to run on IBM hardware. This precludes custom gate definitions and higher-level constructs like gate modifiers (such as inv @) from being valid for execution on hardware verbatim, but the transpile process resolves them into valid ISA circuits. Qiskit SDK (as of July 2025, through qiskit-qasm3-import v0.6.0) will eagerly evaluate gate modifiers during the parse, so these will not be evident in the resulting QuantumCircuit, potentially at a runtime cost.

8. Qiskit SDK can represent structured control flow and export this to OpenQASM 3. The continue and break statements can technically be represented by Qiskit, but are not well supported even within Qiskit SDK. for loops in Qiskit v2.1.0 are not well supported. Nested control flow (such as an if inside another if, or an else if statement) is not eligible for execution on hardware.

9. Qiskit SDK supports declaring any supported classical type as an input variable on the circuit. Such variables are not currently eligible for execution on hardware, and cannot be loaded by the Qiskit OpenQASM 3 importer. Unbound Parameter objects present in the QuantumCircuit are exported as input float[64] variables. Certain runtime configuration options can enable executing such circuits on some backends.

Next steps

Recommendations

• Learn how to generate OpenQASM code using IBM Quantum Composer.
• See the OpenQASM 3 Qiskit API reference.
• See the OpenQASM 2 Qiskit API reference.
• Review the Verify your program topic.
• Visit the OpenQASM Live Specification.