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

Make SabreSwap account for clbits in predecessors (backport #7952) #7957

Merged
merged 1 commit into from
Apr 19, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 19, 2022

This is an automatic backport of pull request #7952 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Make SabreSwap account for clbits in predecessors

Previously, SabreSwap only checked that it was valid to add a gate back
to the DAG by ensuring that all its qubit predecessors had already been
added to the DAG.  It did not check for clbit successors.  This meant
that measurements and (potentially, unverified) classically conditioned
gates could be re-ordered out from the correct topological ordering.

The most notable effect of this was that measurements writing to the
same bit could be re-ordered, changing the output of the circuit.

See gh-7950 for more detail.

* Add reno

* Fix lint

* Trim fat in SabreSwap._successors

Co-authored-by: Matthew Treinish <mtreinish@kortar.org>

* Fix _successors method

Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
(cherry picked from commit 38f3705)
@mergify mergify bot requested a review from a team as a code owner April 19, 2022 19:57
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

  • @Qiskit/terra-core

@mtreinish mtreinish added automerge Changelog: Bugfix Include in the "Fixed" section of the changelog labels Apr 19, 2022
@jakelishman jakelishman added this to the 0.20.1 milestone Apr 19, 2022
@mergify mergify bot merged commit 35645aa into stable/0.20 Apr 19, 2022
@mergify mergify bot deleted the mergify/bp/stable/0.20/pr-7952 branch April 19, 2022 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: Bugfix Include in the "Fixed" section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants