Actions
Bug #6159
closedChecker produces the incorrect constraint for a memory access structure
Start date:
07/08/2015
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
2.2.9
Description
Executions:
LOAD, BYTE, isMapped=1, DTLB.Event=MISS, JTLB.Event=HIT, VA[12]=0, G=1, V=1, D=1, isHiMem=0, C[0:1]=2, STOP,
LOAD, BYTE, isMapped=1, DTLB.Event=MISS, JTLB.Event=HIT, VA[12]=0, G=1, V=1, D=1, isHiMem=0, C[0:1]=2, STOP,
Dependencies:
VAAddrNotEqualPAAddrNotEqualDTLBTagReplaced
Result:
UNSAT
Constraint:
[isMapped$0$[0, 0] = 1],
[VA$0$[12, 12] = 0],
[D$0$[0, 0] = D0$0$[0, 0]],
[V$0$[0, 0] = V0$0$[0, 0]],
[PFN$0$[0, 23] = PFN0$0$[0, 23]],
[C$0$[0, 1] = C0$0$[0, 1]],
[C$0$[2, 2] = C0$0$[2, 2]],
[G$0$[0, 0] = 1],
[V$0$[0, 0] = 1],
[D$0$[0, 0] = 1],
[isHiMem$0$[0, 0] = 0],
[PA$0$[0, 11] = VA$0$[0, 11]],
[PA$0$[12, 35] = PFN$0$[0, 23]],
[C$0$[0, 1] = 2],
[isMapped$1$[0, 0] = 1],
[VA$1$[12, 12] = 0],
[D$1$[0, 0] = D0$1$[0, 0]],
[V$1$[0, 0] = V0$1$[0, 0]],
[PFN$1$[0, 23] = PFN0$1$[0, 23]],
[C$1$[0, 1] = C0$1$[0, 1]],
[C$1$[2, 2] = C0$1$[2, 2]],
[G$1$[0, 0] = 1],
[V$1$[0, 0] = 1],
[D$1$[0, 0] = 1],
[isHiMem$1$[0, 0] = 0],
[PA$1$[0, 11] = VA$1$[0, 11]],
[PA$1$[12, 35] = PFN$1$[0, 23]],
[C$1$[0, 1] = 2],
[VA$0$[0, 11] = VA$1$[0, 11]],
[VA$0$[12, 12] = VA$1$[12, 12]],
[VA$0$[40, 63] = VA$1$[40, 63]],
[PA$0$[0, 11] = PA$1$[0, 11]],
[PA$0$[12, 35] = PA$1$[12, 35]],
[VA$0$[13, 39] = VA$1$[13, 39]],
[VA$0$[13, 39] != VA$1$[13, 39]]
UNSAT
Updated by Alexander Kamkin over 9 years ago
- Status changed from New to Resolved
Refactoring led to a typo:
public static MmuCondition neq(final MmuExpression expression) {
return new MmuCondition(MmuConditionAtom.eq(expression)); // eq -> neq
}
Updated by Andrei Tatarnikov over 9 years ago
- Status changed from Resolved to Closed
- Published in build set to 2.2.9
Actions