Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update quake-dialect.md #1760

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update quake-dialect.md #1760

wants to merge 1 commit into from

Conversation

johnmaxrin
Copy link

Fixed typo: replaced "Quake's memory model" with "QTX's memory model"

Description

Fixed typo: replaced "Quake's memory model" with "QTX's memory model" (previously incorrectly stated as "Quake's memory model").

Fixed typo: replaced "Quake's memory model" with "QTX's memory model"
Copy link

copy-pr-bot bot commented Jun 5, 2024

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Copy link

github-actions bot commented Jun 5, 2024

CLA Assistant Lite bot All Contributors have signed the CLA.

@johnmaxrin
Copy link
Author

I have read the Contributor License Agreement and I hereby accept the Terms.

@johnmaxrin
Copy link
Author

recheck

@@ -28,7 +28,7 @@ greater, the extra qubits are considered controls.
The main motivation behind Quake's value model is to directly expose
quantum and classical data dependencies for optimization purposes,
i.e., to represent the dataflow in quantum computations. In contrast
to Quake's memory model, which uses memory semantics (quantum
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quake is flexible in that it can represent both the memory and value semantics model (switching via the --memtoreg pass). So the text as-is is correct. Granted, the whole document here could use a refresh probably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants