You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// is timestamping off, is it pointer is off, for small source values
439
383
440
384
// Range check len
441
385
let len_bits_limit = [
@@ -651,25 +595,25 @@ where
651
595
// we have saturating sub, which isnt a perfect sub,
652
596
// 0, 4, 20
653
597
// source is tOO SMALL, SO READING SAME DATA TWICE??
654
-
if shift != 0{
655
-
record.var[0].data[3] = tracing_read(
656
-
state.memory,
657
-
RV32_MEMORY_AS,
658
-
source - 4*(source >= 4)asu32,
659
-
&mut record.var[0].read_aux[3].prev_timestamp,
660
-
);
661
-
}else{
662
-
record.var[0].data[3] = tracing_read(
663
-
state.memory,
664
-
RV32_MEMORY_AS,
665
-
source - 4*(source >= 4)asu32,// what happens when we read same memory twice? is it bc not constraining properly? since its the same piece of memory; this error will still happen, if source < 4? since no "previous" word
666
-
&mut record.var[0].read_aux[3].prev_timestamp,
598
+
599
+
record.var[0].data[3] = tracing_read(
600
+
state.memory,
601
+
RV32_MEMORY_AS,
602
+
source - 4*(source >= 4)asu32,
603
+
&mut record.var[0].read_aux[3].prev_timestamp,
604
+
);
605
+
if source < 4{
606
+
eprintln!("preflight shift: {:?}", shift);
607
+
eprintln!("preflight, before saturating sub source: {:?}", source);
608
+
eprintln!("preflight, after saturating sub source: {:?}", source);
0 commit comments