Feature/heir cross integration

[Zohaib58]

Adds end-to-end support for lowering JaxiteWord IR to CROSS (Google’s CKKS backend for TPU), including dialect ops, a crypto-context setup pass, and an expanded Python emitter.

This completes the JaxiteWord → CROSS path that was started in earlier JaxiteWord work. The LWE → JaxiteWord conversion pass is intentionally out of scope here and tracked separately in #2964.

Changes

JaxiteWord dialect

• Extend JaxiteWordOps.td with CROSS-oriented ops (e.g. gen_params, program_initialization, mul/relin/rot helpers aligned with the CROSS API).
• Simplify dialect verification by removing redundant MulOp / RotOp verifiers where TableGen already enforces types/attributes.

jaxiteword-configure-crypto-context pass

• New transform pass that analyzes an entry function and synthesizes helper functions to generate and configure the CROSS crypto context.
• Infers CKKS parameters such as mul depth, rotation indices, and relinearization needs from the IR.
• Exposes pass options for manual overrides (mul depth, TPU tiling r/c, batch size, composite rescaling, scaling factor, etc.).
• JaxiteWord emitter (heir-translate --emit-jaxiteword)
• Substantially expand JaxiteWordEmitter and templates to emit CROSS-compatible Python.
• Cover homomorphic ops (add/sub/mul/relin/rot/mod_reduce, etc.) and crypto setup (gen_params, keygen, eval keys).

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[j2kun]

Let's leave out the MODULE.bazel.lock change. I think you can add it to .git/info/exclude to exclude it from your local git.

[j2kun]

Remove this file. It should not be needed anymore now that we have MODULE.bazel

[j2kun]

You should not need these, and you can remove the corresponding hasVerifier from the ops tablegen.

[j2kun]

@Zohaib58 I think there are still some issues with the rebase.

One thing you could try is, from a fresh branch rebased over main, run wget https://github.com/google/heir/pull/2934.patch to save the prior PR to a patch file, then git apply 2934.patch to apply it to your workspace. Make any additional changes from there and force push to this branch.

[Zohaib58]

@Zohaib58 I think there are still some issues with the rebase.

One thing you could try is, from a fresh branch rebased over main, run wget https://github.com/google/heir/pull/2934.patch to save the prior PR to a patch file, then git apply 2934.patch to apply it to your workspace. Make any additional changes from there and force push to this branch.

Hi Jeremy,

The current PR is missing LWEToJaxiteWord pass. Should I make another commit including that pass? Is there any issue with the LWEToJaxiteWord pass that I need to fix?

[j2kun]

I think I just missed LWEToJaxiteWord in my initial work. Let's put it into a separate PR.

[Zohaib58]

I think I just missed LWEToJaxiteWord in my initial work. Let's put it into a separate PR.

Would you prefer I wait until PR #2946 merges and then open the conversion pass against main, or is it OK to open a separate PR now (stacked on top of this branch / or rebased once this lands)?

[j2kun]

Generally OK to add additional stacked PRs. Keeping the individual PRs smaller makes it easier for me to review them.