Fix RESBM Region Build Error for Multiple Ciphertext Inputs in ONNX Compilation#6
Open
minghan1 wants to merge 3 commits intoant-research:mainfrom
Open
Fix RESBM Region Build Error for Multiple Ciphertext Inputs in ONNX Compilation#6minghan1 wants to merge 3 commits intoant-research:mainfrom
minghan1 wants to merge 3 commits intoant-research:mainfrom
Conversation
suncchan
approved these changes
Jan 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
When processing multiple ciphertext inputs (e.g., in test case hemult2.onnx, which computes a * b * c), the compilation to onnx.c fails with the RESBM error: "region input must be MultCC/MultPC." This occurs because RESBM assigns each ciphertext to a region based on its mul_depth. Since the mul_depth values for ciphertexts a, b, and c differ, ciphertext c is not placed in region1, violating the subsequent requirement that only region1 can accept non-MultCC/MultPC inputs, while all other regions must have MultCC/MultPC inputs.
Solution:
After region creation, force all input ciphertexts to be assigned to region1