Remove sanity-check logic in range summary construction -- zero-length

ranges make this somewhat fickle to verify, and fuzzing will catch any
issues.
This commit is contained in:
Chris Fallin
2021-05-09 01:14:03 -07:00
parent 095a883814
commit 509c5dc2fd

View File

@@ -2994,24 +2994,6 @@ impl<'a, F: Function> Env<'a, F> {
ProgPoint::from_index(0)
};
bundledata.range_summary.bound = CodeRange { from, to };
#[cfg(debug_assertions)]
{
// Sanity check: ensure that ranges returned by the range
// summary correspond to actual ranges.
let mut iter = self.bundles[bundle.index()].first_range;
let mut summary_iter = self.bundles[bundle.index()]
.range_summary
.iter(&self.range_ranges[..]);
while iter.is_valid() {
assert_eq!(
summary_iter.next(),
Some(self.ranges_hot[iter.index()].range)
);
iter = self.ranges_hot[iter.index()].next_in_bundle;
}
assert_eq!(summary_iter.next(), None);
}
}
fn process_bundle(&mut self, bundle: LiveBundleIndex) {