【Decompose】 电路执行顺序问题 #52
-
|
在 Decompose 代码里，有一个地方没明白： 以上是我打印出的各个函数执行的顺序信息， 为什么 MyCircuit 的 synthesize 执行了 2 次？ 第一次 Layouter 没有干事，第二次才开始赋值
这说明第一次执行 fn synthesize(
&self,
config: Self::Config,
mut layouter: impl Layouter<F>,
) -> Result<(), Error> {
println!("MyCircuit - synthesize");
config.table.load(&mut layouter)?;
println!("self.value {:?}",self.value );
let value = layouter.assign_region(
|| "Witness value",
|mut region| {
region.assign_advice(|| "Witness value", config.running_sum, 0, || self.value)
},
)?;
config.assign(
layouter.namespace(|| "synthesize decompose value"),
value, // value 0x9a.
self.num_bits, // 8, the len of binary form of the num `154`.
)?;
Ok(())
} |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
我当时也有这个困惑，我的理解第一次是生成没有witness的电路，第二次是把witness放到里面去。至于为什么这么做，我也不太清楚（模模糊糊感觉是为了做sanity check) |
Beta Was this translation helpful? Give feedback.
-
|
周博神速回复 🤣 |
Beta Was this translation helpful? Give feedback.
-
|
第一次是生成了电路的pk 和vk，所以不会将witness 填入。 |
Beta Was this translation helpful? Give feedback.
-
应该不是 Keygen ，我在这一步加了标识，但是结果显示 synthesize 不是在这里调用的 |
Beta Was this translation helpful? Give feedback.
-
|
What you put here is the callee not caller, which might not buy us any good. Take MockProver as an example
It states clearly. First time it only gets shape of region, while second time it assigns concrete values. |
Beta Was this translation helpful? Give feedback.
-
|
Some comments: |
Beta Was this translation helpful? Give feedback.
-
|
Great Explaination! notice that the impl<F: PrimeField + PrimeFieldBits, const LOOKUP_NUM_BITS: usize, const LOOKUP_RANGE: usize> Circuit<F>
for MyCircuit<F, LOOKUP_NUM_BITS, LOOKUP_RANGE>
{ // DecomposeConfig<F, 10, 1024>
type Config = DecomposeConfig<F, LOOKUP_NUM_BITS, LOOKUP_RANGE>; // <F, LOOKUP_NUM_BITS, LOOKUP_RANGE>
type FloorPlanner = V1;In MockProver::run() println!("----");
ConcreteCircuit::FloorPlanner::synthesize(&mut prover, circuit, config, constants)?;
println!("----");so, in There are 2 passes here :
fn synthesize<F: Field, CS: Assignment<F>, C: Circuit<F>>(
cs: &mut CS,
circuit: &C,
config: C::Config,
constants: Vec<Column<Fixed>>,
) -> Result<(), Error> {
let mut plan = V1Plan::new(cs)?;
// First pass: measure the regions within the circuit.
let mut measure = MeasurementPass::new();
{
let pass = &mut measure;
circuit
.without_witnesses()
.synthesize(config.clone(), V1Pass::<_, CS>::measure(pass))?;
}
/// ...
// Second pass:
// - Assign the regions.
let mut assign = AssignmentPass::new(&mut plan);
{
let pass = &mut assign;
circuit.synthesize(config, V1Pass::assign(pass))?;
} |
Beta Was this translation helpful? Give feedback.
What you put here is the callee not caller, which might not buy us any good.
Take MockProver as an example
call stack: