Adding reset after measure if qubit is to be reused #3450
Conversation
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
1tnguyen
changed the title
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Co-authored-by: Eric Schweitz <[email protected]> Signed-off-by: Thien Nguyen <[email protected]>
Co-authored-by: Eric Schweitz <[email protected]> Signed-off-by: Thien Nguyen <[email protected]>
Co-authored-by: Eric Schweitz <[email protected]> Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
There was a problem hiding this comment.
This pass should be written when the IR is in explicit linear use form (aka, value semantics), as it will be much simpler to understand, write, etc.
It actually becomes trivial. A measurement op must produce 1 or more wires. If those wires are used by anything that is not a sink operation, they are reused. In those case, if the reuse is not a reset operation, then insert a reset operation. Done.
| } | ||
|
|
||
| // No next use is found, check if this is an extracted qubit. | ||
| if (isa<quake::RefType>(qubit.getType())) { |
There was a problem hiding this comment.
In reference semantics, you will have to account for every possible case of aliasing. References can alias.
So it's not as simple as looking at alloca and extract_ref. Correctness here means you have to consider calls, block arguments, various arithmetic operations, dynamic qubit refreences, and so on.
On the other hand, value semantics has already been built and makes all of this much, much easier.
runtime/cudaq/platform/default/rest/helpers/quantinuum/quantinuum.yml
Outdated
Show resolved
Hide resolved
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Thien Nguyen <[email protected]>
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
4 participants
Description
A pass to detect if qubit is to be reused after measurement. If so, insert a
resetand conditionalxgate based on measurement result in order to bring the qubit into the |0> or |1> state consistent with the measurement.Add the pass to
quantinuumtarget pipeline config.Add tests.
Modify the resource counting pre-process pass: move it down the JIT pipeline as the removal of gates in that pass may interfere with the program flow detection (i.e., whether a qubit is reused or not).