-
Notifications
You must be signed in to change notification settings - Fork 206
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
[core] This is a new implementation of QIR codegen. #2542
base: main
Are you sure you want to change the base?
Conversation
76f40bc
to
8949d00
Compare
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
6960e4a
to
f04069e
Compare
shows its age at this point. It was written before much of the rest of the core was implemented or even designed. These changes replace the existing QIR codegen for the C++ compiler. Unfortunately, there are a number of semantics violations from Python that need to be fixed before it can be switched over. Therefore, this PR leaves Python intact and using the old codegen passes. The purpose of these changes is two-fold. 1. Instead of converting all of the IR to the LLVM-IR dialect at the same time as converting to QIR, these two steps are bifurcated. This allows us to convert the quake dialect to other higher level operations first and before LLVM-IR dialect is introduced. This will be beneficial in short order... 2. Instead of piecemealing different flavors of QIR in completely ad hoc spaghetti plate passes, the flavor of QIR is specified as a mixin modifier class for a singular set of steps to convert to any flavor of QIR. This does mean that one will no longer be able to convert to the LLVM-IR dialect with QIR calls and then change their mind from chocolate QIR to strawberry QIR much later. Notes: - Remove the option to disable the qir profile preparation pass. This pass is not optional. The IR will be translated to an invalid state if the required function declarations are not created at all. - Make it clear that AggressiveEarlyInlining is a pipeline. Refactor the registration functions so that we're not block-copying things between the core and python (which was dropping things on the floor already). - Add a new pass, convert to QIR API. This pass will replace the cascade of passes to convert to full QIR and then convert some more to base profile or adaptive profile. - Refactor QIRFunctionNames.h. - Add a raft of declarations to the intrinsics table. This will dramatically reduce the amount of code in codegen and make maintenance much easier. - Add the analysis and prep pass. - Improve pipeline locality and performance. - Use the new code in the default code gen path for C++. - Workarounds for issue NVIDIA#2541 and issue NVIDIA#2539. Keep the old codegen for python. Too many bugs. - Update tests. Fix bugs in mock servers. Have python kernel builder add the cudaq-kernel attribute. (See issue 2541.) Signed-off-by: Eric Schweitz <[email protected]>
f04069e
to
12a59ca
Compare
Signed-off-by: Eric Schweitz <[email protected]>
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Eric Schweitz <[email protected]>
Signed-off-by: Eric Schweitz <[email protected]>
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
std::string{cudaq::opt::QIRCustomOp} + (op.isAdj() ? "__adj" : ""); | ||
std::string qirFunctionName = cudaq::opt::QIRCustomOp; | ||
if (op.isAdj()) | ||
qirFunctionName += "__adj"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use the newly added QIRCustomAdjOp
directly?
The QIR codegen is one of the oldest pieces of the project and really shows its age at this point. It was written before much of the rest of the core was implemented or even designed.
These changes replace the existing QIR codegen for the C++ compiler. Unfortunately, there are a number of semantics violations from Python that need to be fixed before it can be switched over. Therefore, this PR leaves Python intact and using the old codegen passes.
The purpose of these changes is two-fold.