Comment on page
Support and Issues
Concrete ML is a constant work-in-progress, and thus may contain bugs or suboptimal APIs.
Furthermore, undefined behavior may occur if the input-set, which is internally used by the compilation core to set bit-widths of some intermediate data, is not sufficiently representative of the future user inputs. With all the inputs in the input-set, it appears that intermediate data can be represented as an n-bit integer. But, for a particular computation, this same intermediate data needs additional bits to be represented. The FHE execution for this computation will result in an incorrect output, as typically occurs in integer overflows in classical programs.
- the reproducibility rate you see on your side
- any insight you might have on the bug
- any workaround you have been able to find