-
Notifications
You must be signed in to change notification settings - Fork 196
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
attempting to use cudaq.kernels.uccsd
kernel with hardware backend fails at compilation
#2357
Comments
additional context: I believe this to be unique to the
|
Cleaning up the code snippet a little from above:
It works fine for the
|
My bad. I misread "uncomment". Both the original code and Zohim's modified code have issues. ...
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op loop bounds exceed iteration threshold
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op loop bounds exceed iteration threshold
error: 'cc.loop' op not a constant upper bound loop
error: 'cc.loop' op not a constant upper bound loop
... |
As of the latest, this now simply reports |
It's difficult to tell the exact reason for the unrolling failure, but it looks like the compiler isn't recognizing some constant propagation for |
Required prerequisites
Describe the bug
Any program that utilizes
cudaq.kernels.uccsd
against a hardware backend fails during what looks like a MLIR rewrite pass, per the failure output.Steps to reproduce the bug
The following repro case, as written, runs successfully. If you uncomment line 3 or 4 (i.e. set target to a hardware backend), it fails with the output below.
healthy case
failure case output - IonQ
failure case output - IQM
Expected behavior
successful compilation and execution
Is this a regression? If it is, put the last known working version (or commit) here.
Unknown
Environment
Suggestions
No response
The text was updated successfully, but these errors were encountered: