From 831fe862ff207c87d80b3bbe3f5c5ccda450ebbc Mon Sep 17 00:00:00 2001 From: Jacqueline Nabaglo Date: Thu, 27 Jul 2023 15:04:10 -0700 Subject: [PATCH] Cut 5 Columns From The Memory Table With This One Weird Trick! --- evm/src/memory/columns.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/evm/src/memory/columns.rs b/evm/src/memory/columns.rs index 91cc8754..c972dd0a 100644 --- a/evm/src/memory/columns.rs +++ b/evm/src/memory/columns.rs @@ -1,6 +1,6 @@ //! Memory registers. -use crate::memory::{NUM_CHANNELS, VALUE_LIMBS}; +use crate::memory::VALUE_LIMBS; // Columns for memory operations, ordered by (addr, timestamp). /// 1 if this is an actual memory operation, or 0 if it's a padding row. @@ -28,7 +28,7 @@ pub(crate) const SEGMENT_FIRST_CHANGE: usize = CONTEXT_FIRST_CHANGE + 1; pub(crate) const VIRTUAL_FIRST_CHANGE: usize = SEGMENT_FIRST_CHANGE + 1; // We use a range check to enforce the ordering. -pub(crate) const RANGE_CHECK: usize = VIRTUAL_FIRST_CHANGE + NUM_CHANNELS; +pub(crate) const RANGE_CHECK: usize = VIRTUAL_FIRST_CHANGE + 1; // The counter column (used for the range check) starts from 0 and increments. pub(crate) const COUNTER: usize = RANGE_CHECK + 1; // Helper columns for the permutation argument used to enforce the range check.