Sara/hybrid phase folding - #3122
Draft
sarababaeii wants to merge 75 commits into
Draft
Conversation
…2894) **Context:** We introduce `qecl.fabricate [magic]` in the QEC Logical layer, and want to lower it to a subroutine for encoding a codeblock in the magic state in the QEC Physical dialect. This subroutine will eventually be performed by a magic state factory rather than being included in the IR, but including it allows us to validate our processes via simulator. We will not inject noise into the magic state fabrication subroutine, so this does not need to be implemented in a fault-tolerant manner. **Description of the Change:** We add lowering for putting a code-block in the magic state based on the unitary encoding for the ground-state of the codeblock. Note that the unitary rather than measurement-based encoding must be used, because the measurement-based encoding projects the codeblock into the code space, but the magic state exists outside the code space. We also fix a bug from the previous (QEC Logical level) PR for `fabricate [magic]`, where the op is used in the `apply_T` subroutine. The conditional `SX` correction was added in the wrong order. **Benefits:** We can lower `qecl.fabricate` to something that can be executed on a simulator to create a codeblock in the magic state. **Possible drawbacks:** We don't lower `fabricate` to a magic-state distillation protocol, so its not mimicking the instructions for hardware; this could be a source of confusion if not communicated clearly. Also, it's likely that we will eventually lower this op to `qecp.fabricate` instead of including instructions for "fabrication" in the IR - the fabrication instructions will already be known in the magic-state factory, and we will be interfacing with it. However, for exploration and validation, this is the solution most suited to our current needs. --------- Co-authored-by: Joey Carter <joseph.carter@xanadu.ai> Co-authored-by: Joey Carter <joey.snarrcarter@gmail.com>
…2895) **Context:** We have 3 ops that we add to the IR for creating and using magic states that need to be translated back to the `quantum` dialect for execution. These are: - `allocate_cb`: to create an additional auxiliary codeblock that we can put in the magic state - `deallocate_cb`: to deallocate the data codeblock after the entanglement and measurement protocol teleports the data to the allocated auxiliary codeblock (new data codeblock) - `t`: used on a single physical qubit in the subroutine for generating a magic state on the auxiliary codeblock **Description of the Change:** We add lowering for: - `allocate_cb`: translates to allocating a quantum register of size `n` - `deallocate_cb`: translates to deallocating a quantum register - `t`: translates to `quantum.custom "T"` We add integration tests to confirm that this and previous PRs for `apply_T` and `fabricate_magic_state` allow us to apply T gates in the Steane code as expected. **Benefits:** We can execute circuits with T-gates using the Steane code We have the pieces in place to lower other protocols fabricating and using magic states, like pi/8 PPMs --------- Co-authored-by: Joey Carter <joseph.carter@xanadu.ai> Co-authored-by: Joey Carter <joey.snarrcarter@gmail.com>
A static conditional can be evaluated trivially at trace time since it doesn't really have a reason to exist. Static loops still serve the purpose of compacting the program, but will introduce additional dynamic variables. In some conditions resolving these at trace time can also be desirable. The toggle is global because in the context where the decision is made we don't have access to QJIT-instance specific compilation options. This is the simplest way forward, although alternatives could expand the EvaluationContext with a reference to the currently active `CompileOptions` in the future (for example). [sc-121161] --------- Co-authored-by: Isaac De Vlugt <34751083+isaacdevlugt@users.noreply.github.com>
…2923) **Context:** In order to analyze resources the operations must be in value semantics, which requires a conversion step for any op in reference semantics. **Description of the Change:** Adds direct support for reference semantics to the `resource-analysis` pass and underlying class. **Benefits:** Conversions are no longer needed for resource analysis. **Possible Drawbacks:** **Related GitHub Issues:** [sc-121611] --------- Co-authored-by: paul0403 <paulhaochen.wang@gmail.com>
**Context:** When translating to the `qecp` dialect, we currently only generate a subroutine for `S`, and not for adjoint S. **Description of the Change:** We add support for adjoint S. We add a subroutine by adding an `s_adj` in the `QecCode` definition for `Steane`, and we map `qecl.s %0 adj` to `s_adj` instead of `s` when selecting a subroutine. Currently S is the only qecl logical op that can have adjoint=True, but if other ops are added in the future, they can similarly have their lowering defined by adding `opname_adj` to the `QecCode`. **Benefits:** We can use logical `adjoint(S)` and get correct results. [sc-121126] --------- Co-authored-by: Joey Carter <joseph.carter@xanadu.ai>
**Context:** Remove libboost-dev src installation dep. Tested locally and on manylinux_2_28 x86/aarch64 **Description of the Change:** **Benefits:** - Remove libboost-dev src installation dep on CIs - No impacts on wheels recipes. **Possible Drawbacks:** **Related GitHub Issues:** [sc-121685]
… flat circuits (#2920) **Context:** Implement the conversion pass from value semantics to reference semantics. To relieve review pressure, I'll again split into multiple PRs: flat circuits (alloc, gates, observables), regioned ops (control flow + adjoint), and subroutines. **Description of the Change:** The logic and code structure is essentially just a "conjugated" `--convert-to-value-semantics` pass, but much easier, since we don't need to build the extract/insert quantum dataflow. Essentially, a map keeps track of what `qref` references each value semantics qubit/qreg SSA value corresponds to. At each quantum operation, e.g. ```mlir %out_qubit = quantum.custom "gate" %in_qubit ``` the map is cascaded forward via ``` v_to_r_map[%out_qubit] = v_to_r_map[%in_qubit] ``` Note that this way of cascading forward saves the time needed to repeatedly walk back the chain every time a new quantum value is visited. **Benefits:** We have full qref support! With both directions' conversion in place, pass implementors can freely choose the semantics they want. **Possible Drawbacks:** None [sc-105534] --------- Co-authored-by: Mehrdad Malek <39844030+mehrdad2m@users.noreply.github.com>
added 28 commits
August 3, 2026 17:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before submitting
Please complete the following checklist when submitting a PR:
All new functions and code must be clearly commented and documented.
Ensure that code is properly formatted by running
make format.The latest version of black and
clang-format-20are used in CI/CD to check formatting.All new features must include a unit test.
Integration and frontend tests should be added to
frontend/test,Quantum dialect and MLIR tests should be added to
mlir/test, andRuntime tests should be added to
runtime/tests.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
the input program should be in Clifford+T
Description of the Change:
Implements [sc-122685], [sc-122686], and [sc-122687]
Benefits:
Possible Drawbacks:
Does not support registers as function argument or over control flow
Can't understand state preparation as they become dynamic values in mlir
Related GitHub Issues: