Fix hasty change about end invariants
Some checks failed
Tests / Clang total: 1776, passed: 1776
Clang |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Tests / SIMD fallback total: 1776, passed: 1776
Tests / 32-bit versions total: 1776, passed: 1776
Tests / Release [gcc] total: 1776, passed: 1776
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Tests / Release [gcc,aarch64] total: 1327, passed: 1327
Tests / Coverage total: 1333, passed: 1333
Code Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 98.05% (1510/1540) * Branch Coverage: 65.14% (1405/2157) * Complexity Density: 0.00% * Lines of Code: 1540 #### Quality Gates Summary Output truncated.
weaselab/conflict-set/pipeline/head There was a failure building this commit

`end` is allowed to be <= 0 at the beginning of
checkMaxBetweenExclusive, but not later after checking for the first
range version.
This commit is contained in:
2024-06-30 21:20:05 -07:00
parent 2646d5eaf1
commit 66bd799f05

View File

@@ -1967,7 +1967,7 @@ bool checkMaxBetweenExclusive(Node *n, int begin, int end,
InternalVersionT readVersion) {
assume(-1 <= begin);
assume(begin <= 256);
assume(0 < end);
assume(-1 <= end);
assume(end <= 256);
assume(begin < end);