worldfnd / worldfnd/provekit

Build fails with invalid AArch64 register errors in block-multiplier during proof generation

Open
#137 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Noir
Stars
138
Forks
47
Avg merge
1d 34m
Merged PRs (30d)
6

Description

Hi team,

I'm encountering a compilation issue when trying to generate a proof using the following command:

cargo run --release --bin noir-r1cs prepare ./target/basic.json -o ./noir-proof-scheme.nps

The build fails with multiple register-related errors coming from block-multiplier/src/aarch64/mod.rs. Here's a sample of the output:

...
error: invalid register v16: unknown register
   --> block-multiplier/src/aarch64/mod.rs:212:31
    |
212 |             lateout("v15") _, lateout("v16") _, lateout("v17") _, lateout("v18") _,
    |                               ^^^^^^^^^^^^^^^

error: invalid register v17: unknown register
   --> block-multiplier/src/aarch64/mod.rs:212:49

error: invalid register v18: unknown register
   --> block-multiplier/src/aarch64/mod.rs:212:67

error: invalid register v19: unknown register
   --> block-multiplier/src/aarch64/mod.rs:213:13

error: invalid register lr: unknown register
   --> block-multiplier/src/aarch64/mod.rs:213:31
...

System info:

OS: Linux kali 6.12.25-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.12.25-1kali1 (2025-04-30) x86_64 GNU/Linux

Rust version: rustc 1.88.0-nightly (17ffbc81a 2025-04-04)

Thank you in advance for your help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported cargo run command and inspect block-multiplier/src/aarch64/mod.rs around lines 212-213. Compare the AArch64 register usage with the reported x86_64 environment and Rust toolchain configuration. Done means the project builds and proof generation completes without invalid-register errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.