-
Notifications
You must be signed in to change notification settings - Fork 33
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
Generate a helper that configures OpenFHE crypto context based on the IR content #661
Comments
This issue has 2 outstanding TODOs:
This comment was autogenerated by todo-backlinks |
I've looked over this issue, and I would like to give it a try :) |
Also one more note: we can add the pub/priv key generation to the context generation function (#696 (comment)), if we remove the restriction to return only one value. Maybe something like:
or it could go in configure |
After removing that restriction, we also can remove the return parameter in configure_crypto_context. See #696 (comment) |
Before I forget, I would like to seek some advice and explain what I have attempted so far. First, I thought it would be easy to implement dataflow analysis for both If I understand correctly,
I'm not very familiar with C++ and mlir, so these might be dumb questions. Any comments are welcome! |
I don't necessarily think you should use IntRangeAnalysis directly for this. If I were you I would write a new analysis that uses the same base framework (I'm mobile so I forget the name, something like AbstractForwardDataflowAnalysis, we have some examples already in HEIR I believe). |
Awesome, thank you for your comments! I will take a closer look. |
Right now the user must manually call functions like
EvalMultKeyGen
if the IR containsEvalMult
, andEvalRotateKeyGen
with known rotation shifts (which requires looking at the generated code to determine), as well asSetMultiplicativeDepth
andSetPlaintextModulus
.We should have a pass in the OpenFHE dialect that generates a function that configures the
cryptoContext
appropriately.The text was updated successfully, but these errors were encountered: