-
Notifications
You must be signed in to change notification settings - Fork 75
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
rename and split --tosa-to-boolean-XYZ to --mlir-to-scheme plus --to-BACKEND #1573
Comments
Just a note, in arithmetic pipeline the backend passes are named
Agree on this. |
Ah gotcha, --mlir-to-cggi and --scheme-to-XYZ backend for now. |
+1, Muthu asked on discord this morning how to convert an IR like this
To tfhe-rs, and I realized that our only pipeline that handles this is called |
Follow-ups: * I'd also like to unify the arith-to-cggi (non-Yosys) paths with the `--mlir-to-cggi` but I don't know how possible it is given the compile time yosys dependency. I think I could make it work, tbh. In a follow-up #1646 * All the backends that support parallism should use the JaxiteBackendOptions, for now I just wanted to maintain parity with the codebase so only the jaxite pipeline has this option. #1645 fixes #1573 PiperOrigin-RevId: 741191624
Follow-ups: * I'd also like to unify the arith-to-cggi (non-Yosys) paths with the `--mlir-to-cggi` but I don't know how possible it is given the compile time yosys dependency. I think I could make it work, tbh. In a follow-up #1646 * All the backends that support parallism should use the JaxiteBackendOptions, for now I just wanted to maintain parity with the codebase so only the jaxite pipeline has this option. #1645 fixes #1573 PiperOrigin-RevId: 741191624
Follow-ups: * I'd also like to unify the arith-to-cggi (non-Yosys) paths with the `--mlir-to-cggi` but I don't know how possible it is given the compile time yosys dependency. I think I could make it work, tbh. In a follow-up #1646 * All the backends that support parallism should use the JaxiteBackendOptions, for now I just wanted to maintain parity with the codebase so only the jaxite pipeline has this option. #1645 fixes #1573 PiperOrigin-RevId: 741191624
Follow-ups: * I'd also like to unify the arith-to-cggi (non-Yosys) paths with the `--mlir-to-cggi` but I don't know how possible it is given the compile time yosys dependency. I think I could make it work, tbh. In a follow-up #1646 * All the backends that support parallism should use the JaxiteBackendOptions, for now I just wanted to maintain parity with the codebase so only the jaxite pipeline has this option. #1645 fixes #1573 PiperOrigin-RevId: 741191624
Follow-ups: * I'd also like to unify the arith-to-cggi (non-Yosys) paths with the `--mlir-to-cggi` but I don't know how possible it is given the compile time yosys dependency. I think I could make it work, tbh. In a follow-up #1646 * All the backends that support parallism should use the JaxiteBackendOptions, for now I just wanted to maintain parity with the codebase so only the jaxite pipeline has this option. #1645 fixes #1573 PiperOrigin-RevId: 741191624
Where backend could be
--to-tfhe-rust-cpu
--to-tfhe-rust-fpt
--to-jaxite
And there are a few options to mlir-to-scheme on whether to use boolean gates or lut3s and the options to vectorize.
As a first step I can split it into
--mlir-to-cggi
to match with our other RLWE schemes?WDYT?
Somewhat related to #1417 #1420
and aids me to integrate it into the frontend
The text was updated successfully, but these errors were encountered: