Determine which backends support ct-pt operations before relinearization
Open
- Dominant language
- MLIR
- Stars
- 906
- Forks
- 171
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 32
Description
Follow up from #3140:
OpenFHE doesn't support ct-pt addition with lazy relinearization. #3148 constrains all ct-pt ops to have linear key basis in optimize-relinearization, but we should make this something backend-configurable (https://github.com/google/heir/issues/2554), as well as determine which backends (if any!) support it.
Contributor guide
Research direction
Start with the context in #3140 and the constraint introduced by #3148, then inspect optimize-relinearization and the backend implementations for ct-pt operations. Compare which backends support ct-pt operations before relinearization and make that capability backend-configurable, with coverage showing the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100