-
Notifications
You must be signed in to change notification settings - Fork 184
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
Unit test failure: test/NVQPP/qir_test_cond_for_break.cpp #781
Comments
schweitzpgi
added a commit
to schweitzpgi/cuda-quantum
that referenced
this issue
Oct 17, 2023
…asurement. Due to an interaction between the revised memtoreg pass and loop unrolling, the test with a mid-circuit measurement and a break statement still wasn't being unrolled. These changes fix that issue. Primarily, these changes allow structured operations that accept region arguments to straddle the fence and allow some values to be promoted as dominating uses (when only used) while other values to be threaded as region arguments exactly as before (when written). This change simplifies the register-semantics IR. There may be a bit of performance lossage in memtoreg as a result however as promoted values may later be discovered to be written and the changes will need to be reapplied.
schweitzpgi
added a commit
to schweitzpgi/cuda-quantum
that referenced
this issue
Oct 17, 2023
…asurement. Due to an interaction between the revised memtoreg pass and loop unrolling, the test with a mid-circuit measurement and a break statement still wasn't being unrolled. These changes fix that issue. Primarily, these changes allow structured operations that accept region arguments to straddle the fence and allow some values to be promoted as dominating uses (when only used) while other values to be threaded as region arguments exactly as before (when written). This change simplifies the register-semantics IR. There may be a bit of performance lossage in memtoreg as a result however as promoted values may later be discovered to be written and the changes will need to be reapplied.
schweitzpgi
added a commit
to schweitzpgi/cuda-quantum
that referenced
this issue
Oct 18, 2023
…asurement. Due to an interaction between the revised memtoreg pass and loop unrolling, the test with a mid-circuit measurement and a break statement still wasn't being unrolled. These changes fix that issue. Primarily, these changes allow structured operations that accept region arguments to straddle the fence and allow some values to be promoted as dominating uses (when only used) while other values to be threaded as region arguments exactly as before (when written). This change simplifies the register-semantics IR. There may be a bit of performance lossage in memtoreg as a result however as promoted values may later be discovered to be written and the changes will need to be reapplied. Leave static unrolling pass in the kernel builder.
MarkusPfundstein
pushed a commit
to fermioniq/cuda-quantum
that referenced
this issue
Sep 23, 2024
…asurement. (NVIDIA#787) Due to an interaction between the revised memtoreg pass and loop unrolling, the test with a mid-circuit measurement and a break statement still wasn't being unrolled. These changes fix that issue. Primarily, these changes allow structured operations that accept region arguments to straddle the fence and allow some values to be promoted as dominating uses (when only used) while other values to be threaded as region arguments exactly as before (when written). This change simplifies the register-semantics IR. There may be a bit of performance lossage in memtoreg as a result however as promoted values may later be discovered to be written and the changes will need to be reapplied. Leave static unrolling pass in the kernel builder.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required prerequisites
Describe the bug
PR #741 added support for the Adaptive Profile, but it added a new test that did not pass yet. The test is marked as
XFAIL
, which allows the CI to know this is an expected failure. This issue captures that issue and is a placeholder for future work.Steps to reproduce the bug
Run the commands captured at the top of
test/NVQPP/qir_test_cond_for_break.cpp
.Expected behavior
The unit test should be able to successfully run to completion without failure.
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
Suggestions
No response
The text was updated successfully, but these errors were encountered: